Menu
▾
▴
FW: [Xenocide-programming] Questions about build environment(s) and devpack(s)
|
From: mamutas <ma...@pr...> - 2003-09-11 02:02:19
|
Here are the answers from the forum just for historical reasons. The devpack idea is rather new (2 or 3 months), however as in every Open Source development you are not forced to work in specified enviroment. = As a difference with other projects we have something to fear if for instance Atari (You know them) wants to shutdown the project because of copyright infridgement of something as had happened to other Open Source projects. = So we have our LEGAL BOUGHT copy of the compiler to release in binary and = that is BCB6. So anyone is free to create a similar one to every compiler as = long as we dont officially build with them. Code is code, however a binary is another thing.=20 About being in the CVS we though to do that, but CVS do not have binary compatibility for difs and until we dont have a Stable one we are = keeping them outside. Our space in sourceforge is finite and storing lots of = binary files with multiple versions in there is space wise. If you have any further question, just ask. Greetings Red Knight=20 QUOTE (nmefford @ Sep 10 2003, 11:28 AM)=20 1) Please clarify unambiguosly what the officially supported build environment(s) and devpack(s) are. Where can I get them? =20 Officially supported build environment is Borland C Builder 6 Personal Edition. As RK mentioned we have bought an official license and we will = use it for all our releases. QUOTE (nmefford @ Sep 10 2003, 11:28 AM)=20 2) What is the level of interest in a VC6 / .NET / .NET 2003 devpack, however official that may be? Please note that .NET project files are incompatible with VC6, and .NET 2003 project files are incompatible with .NET 2002. Not sure about lib files generated with each one. =20 It seemed to be quite popular among project members. I personally like = it better than BCB6. However, due to fact that our final code must compile = on BCB6, there were only private efforts to convert our code from BCB6 to = MSVC. You are the first one who succeeded in that, as far as I know. = Additionally, there is a concern that if developers will start to modify code in CVS = using one IDE, it might broke the functionality (and even compilation) for developers who is using other IDEs. Noone can guarantee that the code = will work with other compilers until code is tested there. QUOTE (nmefford @ Sep 10 2003, 11:28 AM)=20 3) Why are the devpack(s) not in CVS? They could each be in, for = example /xenocide/devpack_bcb6, /xenocide/devpack_NET, etc. Then to build, you simply rename that directory to /devpack and build away. I personally = think it's VERY important that the build files exist in CVS since they are necessarily tightly coupled to the source in CVS. It also helps to have history on these files as sometimes things go haywire with them. It = also would be nice to get everything required to build the project from one location. Finally, I _know_ I duplicated some of your work in getting = .NET 2003 up and running. As well, it would be hard to share that work if = the files were not in some version control repository somewhere.=20 I understood that you meant to keep project files as well as binaries. = RK has already explained about binary constriction we have. As regarding to project file, then it is quite possible, but great care should be taken = when someone modifies the file so not to break other developers = configuration. I guess it could be achieved by imposing some rules, environment = variables, etc. However, BCB6 inserts entries for directories without explicit programmer actions. So, I am very cautios about that too. Please suggest ways how we can go around those issues if you can think = of any. Also, could you please share that working devpack for MSVC? Mamutas P.S. Why do I need to change email address to xen...@li..., when I just hit a reply? Is = the a way to fix it? -----Original Message----- From: xen...@li... [mailto:xen...@li...] On Behalf Of Mefford, Nathan Sent: Wednesday, September 10, 2003 11:20 AM To: 'xen...@li...' Subject: [Xenocide-programming] Questions about build environment(s) and devpack(s) I posted this in the forums, but I think it's important enough to make = my first post here with it as well. Sorry to duplicate the information. = What is a better place to make a post like this? Hi, I don't want to beat a dead horse here, since this topic has = generated a fairly large amount of discussion already, but what is the current = official stance on the supported build environments? I downloaded the VCNetdevpack a few days ago, and got the entire game = and all examples building and running. However, I had to make 3 or 4 changes = to the code from CVS (I actually used .NET 2003, which has significantly = better ANSI compliance than .NET and, as I understand it, BCB6) for the compile = to work. I also had to get a new version of nvparse and build and link to that = lib, which caused a slew of link errors that required that I make one final correction to the code. All in all, it took around 4 hours (it would have taken WAY longer if somebody hadn't already done a lot of the groundwork first). So I have it all up and running now, but I don't want to have to spend = an hour every time I get latest code from CVS reconfiguring project = settings, creating new projects, finding libs compatible with .NET, etc. So here are my actual questions/points 1) Please clarify unambiguosly what the officially supported build environment(s) and devpack(s) are. Where can I get the devpacks? 2) What is the level of interest in a VC6 / .NET / .NET 2003 devpack, however official that may be? Please note that .NET project files are incompatible with VC6, and .NET 2003 project files are incompatible with .NET 2002. Not sure about lib files generated with each one. 3) Why are the devpack(s) not in CVS? They could each be in, for example /xenocide/devpack_bcb6, /xenocide/devpack_NET, etc. Then to build, you simply rename that directory to /devpack and build away. I personally = think it's VERY important that the build files exist in CVS since they are necessarily tightly coupled to the source in CVS. It also helps to have history on these files as sometimes things go haywire with them. It also would be nice to get everything required to build the project from one location. Finally, I _know_ I duplicated some of your work in getting = .NET 2003 up and running. As well, it would be hard to share that work if the files were not in some version control repository somewhere. Well, I guess that's my first contribution to the programming discussion board. I just really want to help make the barrier to contribution on = this project as low as possible. ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Xenocide-programming mailing list = Xen...@li... https://lists.sourceforge.net/lists/listinfo/xenocide-programming --- Incoming mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.514 / Virus Database: 312 - Release Date: 2003/08/28 =20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.514 / Virus Database: 312 - Release Date: 2003/08/28 =20 --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.514 / Virus Database: 312 - Release Date: 2003/08/28 =20 |
