Autotools build system

[greebo]

Ah, thanks, I'll try to look into it next time I'm working in Linux.

[Baal]

Instead of starting a new thread I post that here:

I have made code::blocks project files for the editor as I ran into problems with Win2K (VS 2008 doesn't support it. Surprise!)

They are pretty basic and I'm not sure if everything is set up right but maybe someone finds them usefull.

[greebo]

Well, if you're willing to maintain the files, I can create a folder in the darkradiant/tools/ directory in SVN.

 

Apart from that, I think you can also downgrade VC++ 2008 solution files to VC++ 2005, can't you?

[Baal]

Well, if you're willing to maintain the files, I can create a folder in the darkradiant/tools/ directory in SVN.

Yes, I can do that. They already work on windows with the Microsoft compiler but they need tweaking.

 

Apart from that, I think you can also downgrade VC++ 2008 solution files to VC++ 2005, can't you?

I can manually change the version number of the project files and open them with VC 2005 but I wanted to try codeblocks.

[greebo]

Are the code::blocks files binaries or text files? If they are text files, could you send me a patch with the appropriate files in the tools/ folder?

[Baal]

I uploaded the files to my folder in the betamapper repository (I can't upload them here).

[greebo]

Thanks for the files, I uploaded them to the repository. I guess you need to watch the repository somehow, to get notified about code commits affecting the code::blocks projects. Are you subscribed to the DarkRadiant SVN mailer?

[Baal]

Are you subscribed to the DarkRadiant SVN mailer?

I am now.

 

What's the best way to send you patches? I can't upload files (except images) to the forum.

[greebo]

Either by mail (greebo@angua.at) or by posting them directly. If your commits prove to be trustworthy, I can also give you SVN commit rights.

[greebo]

Ok, it seems our audience has been widening recently - more and more D3 mappers seem to be aware of DarkRadiant, which is nice.

 

Somebody new has reported the lack of Linux binaries on the website, which is about correct. I tried to follow the guide OrbWeaver gave me earlier, but this produced the following:

 

darkradiant_0.9.12-1_amd64.deb

darkradiant-plugins-darkmod_0.9.12-1_amd64.deb

 

Which is apparently the x64 version. How would I proceed building 32-bit binaries? How can I test whether these are even working on other machines?

 

(Although I must confess that my interest in that .deb process is fairly low - switching to Linux is always some kind of hassle as it is not my primary working environment. I'm always waiting for SVN updates, Ubuntu updates and full recompiles before I can finally start doing something - I'd really prefer if somebody else could take care of the linux side of things. Everything is so cumbersome and it feels like I'm wasting my time. Rant over.)

[Tels]

Ok, it seems our audience has been widening recently - more and more D3 mappers seem to be aware of DarkRadiant, which is nice.

 

Somebody new has reported the lack of Linux binaries on the website, which is about correct. I tried to follow the guide OrbWeaver gave me earlier, but this produced the following:

 

darkradiant_0.9.12-1_amd64.deb

darkradiant-plugins-darkmod_0.9.12-1_amd64.deb

 

Which is apparently the x64 version.

 

AFAIK you need a 32bit machine for that. I have one

 

How would I proceed building 32-bit binaries? How can I test whether these are even working on other machines?

 

Using virtualbox Edit: http://www.virtualbox.org/ However note that to run a 64bit virtual box on a computer, you need a 64bit CPU. The other way (running a 32bit virtual box on a 64bit CPU) round works, tho.

 

I have one presetup with the full build environment, it is a bit big to host on bloodgate.com, tho.

 

Edit: But maybe we can push it once via FTP or so? The box can simply be booted, you run "svn update", then "dpkg build-package" (or whatever it was named) and it does the rest.

 

(Although I must confess that my interest in that .deb process is fairly low - switching to Linux is always some kind of hassle as it is not my primary working environment. I'm always waiting for SVN updates, Ubuntu updates and full recompiles before I can finally start doing something - I'd really prefer if somebody else could take care of the linux side of things. Everything is so cumbersome and it feels like I'm wasting my time. Rant over.)

 

I can easily build linux deb files and put them into our repository, however, I don't check the forum everyday and might miss something, so the best way is to PM me about it

 

Edit: Linking to our wiki article about using the repository from the SF page would be a first step, too.

 

http://wiki.thedarkmod.com/index.php/Repository

[greebo]

Ok, I've linked the repository how-to from the sourceforge project web site.

[OrbWeaver]

I can easily build the 32-bit DEBs from my work machine -- it is a nice fast Core 2 Quad machine which I used for all my development work (unlike the shitty single-core P4 I have at home). The only reason I haven't uploaded them to the repository yet is because I haven't got round to digging out my Bloodgate FTP password or re-figuring out the APT repository update process, but I will do that soon if Tels doesn't beat me to it.

[Tels]

I can easily build the 32-bit DEBs from my work machine -- it is a nice fast Core 2 Quad machine which I used for all my development work (unlike the shitty single-core P4 I have at home). The only reason I haven't uploaded them to the repository yet is because I haven't got round to digging out my Bloodgate FTP password or re-figuring out the APT repository update process, but I will do that soon if Tels doesn't beat me to it.

 

I can't send you your FTP password since I only have it at home (I could set a new one, or just wait until monday, then I PM it to you again)

 

I now added a .DEB into the repository for hardy (8.04) 32bit. The other versions (64bit and jaunty/intrepid etc) are still missing, so feel free to upload them.

 

The repository should be explained at the wiki - if not I will expand the article this night or monday.