|
Application Naming |
Posted on: 2017/2/17 22:20
#1 |
---|---|---|
Just popping in
![]() ![]() Joined:
2017/1/3 6:03 From Atlanta GA
Posts: 44
|
I am in process of porting a compiler and am curious as to application naming. Since I don't see the Amiga changes merged back into the main repository what is considered the generally accepted naming.
I see a lot of AmiThis or AmiThat. Would that be best direction for a fork? Thanks Doug |
|
|
Re: Application Naming |
Posted on: 2017/2/17 22:52
#2 |
---|---|---|
Just can't stay away
![]() ![]() Joined:
2006/12/1 18:01 From Copenhagen, Denmark
Posts: 1112
|
You could just keep the name - e.g. GCC is also called GCC in the AmigaOS port.
Best regards, Niels |
|
|
Re: Application Naming |
Posted on: 2017/2/18 1:15
#3 |
---|---|---|
Home away from home
![]() ![]() Joined:
2006/12/4 23:15 Posts: 2145
|
@DStastny
If it's a compiler of some kind, definitly keep the same name, unless there is a copyrights /tradmark issue. |
|
|
Re: Application Naming |
Posted on: 2017/2/18 10:45
#4 |
---|---|---|
Home away from home
![]() ![]() Joined:
2006/11/20 16:26 From Norway
Posts: 2740
|
@DStastny
"Since I don't see the Amiga changes merged back into the main repository what is considered the generally accepted naming." So you did not make changes, and you say you ported it? ha ha… The definition of porting is make changes to make it work on different system ![]() I don't know what compiler you taking about, but if was vasm. I compiled VASM the other day, the only changes I made was in the makefiles.. So the compiler should produce the binaries I need, (HUNK/680x0). I compiled VSAM with GCC, so the result is a PPC/ELF compiler producing 680x0/HUNK files. The normal version of VASM. Is a PPC/ELF compiler that produces PPC/ELF binraries. or 680x0/HUNK compiler that produces 680x0/HUNK binraries Because I did not produce a normal vasm, it find it useful to name it some thing else "AmigaOS4_Cross_Compiler_vasmm68k_mot". I was going to push back git-hub but have not, I was not sure it was the right place to make the changes. If you managed to compile vasm from my repo without the changes, then well I guess you did not need it anyway. Or might just downloaded the compiled vasm version from, my hippoplayer fork. Edited by LiveForIt on 2017/2/18 11:01:09
|
|
_________________
(NutsAboutAmiga) Basilisk II for AmigaOS4 AmigaInputAnywhere Excalibur and other tools and apps. |
||
|
Re: Application Naming |
Posted on: 2017/2/18 11:45
#5 |
---|---|---|
Home away from home
![]() ![]() Joined:
2007/5/19 13:23 From England
Posts: 3553
|
@DStastny
IMHO, keep the name the same, unless you made big changes/improvements to functionality. Otherwise it's just confusing to have different names for the same thing (albiet on different Oses). And names like "AmiWhatever" tend to be for programs written from the ground-up for the Amiga (perhaps copying the appearance or behaviour of a Windows program), not for ports. |
|
_________________
Author of the PortablE programming language. I love using Amiga OS4.1 ![]() It is pitch black. You are likely to be eaten by a grue... |
||
|
Re: Application Naming |
Posted on: 2017/2/18 13:01
#6 |
---|---|---|
Home away from home
![]() ![]() Joined:
2006/12/4 23:15 Posts: 2145
|
@LiveForIt
Quote:
I think you read that worng, he's saying that he doesn't expect the changes he made to be merged "upstream" which is often the case. |
|
|
Re: Application Naming |
Posted on: 2017/2/18 15:55
#7 |
---|---|---|
Just popping in
![]() ![]() Joined:
2017/1/3 6:03 From Atlanta GA
Posts: 44
|
@broadblues
Thank you for clarifying you are correct. @LiveForIt your real friendly fellow. Thank you all for inputs sounds like just keeping the fork in GIT will be direction I take. Regards Doug |
|
|
Re: Application Naming |
Posted on: 2017/2/18 17:17
#8 |
---|---|---|
Amigans Defender
![]() ![]() Joined:
2006/11/17 22:40 From England
Posts: 3228
|
@DStastny
Quote: Since I don't see the Amiga changes merged back into the main repository Please at least make an effort to get your changes merged upstream. Open source maintainers are usually happy to merge changes for obscure machines and often comment that they used to own an Amiga. ![]() There are far too many applications ported to the Amiga where the changes have to be applied again, every time there's a new version, just because the changes have not been merged back (and most likely have not even been attempted to be merged back). |
|