[aldacron]

I just committed the new build scripts I knocked up for Windows. They've been sitting on my harddrive for a few days now waiting for me to upload them. So now they are in. However, I haven't yet removed the Makefiles from the project. I want to ensure that the batch files work as well for others as they do on my system. So if you are a Windows user, please give the batch files a go and let me know how they work out. Here's what you need to do to use them:

1) Grab the latest version of Derek Parnell's Build for Windows.

2) Open up buildconfig.bat in the Derelict trunk. You can read the comments to see how to config everything, but I'll summarize here:

i) if you did not put Build on your path, edit the following line so that it contains the full path to your build executable:
set BUILD_PATH=build.exe (ex: set BUILD_PATH=C:\build\build.exe)

ii) by default, the scripts will build a debug version of each library. You can change the default behavior by changing the following line:
set BRF=build_dbg.brf
to this:
set BRF=build_release.brf
You can also pass the command line args dbg or release to the buildme script to force one mode or the other.

iii) if you wish to specify any command line args to build or dmd in both debug and release modes, then add them to the following line:
set COMMON_ARGS=-cleanup -IDerelictUtil -allobj -full @?BRF?
You may also remove the -cleanup arg if you really want to, but I removing any of the rest will break the build.
Note that debug mode command line args are listed in build_dbg.brf while release mode command line args are listed in build_release.brf.

3) Open up a command prompt (start->run->cmd.exe on Win2k/WinXP, start->run->command.com on Win9X)

4) cd to the toplevel Derelict directory and execute the following command line:
buildme [dbg | release]
OR
cd to the directory of a specific Derelict package and execute the same command line:
buildme [dbg | release]

Very simple. If you have Build on your PATH, and you are happy with the default configuration (which you should be), then you can skip straight to step 3.

Note that the reason I have the build response files (build_dbg.brf and build_release.brf) is that I wanted to share the same command line args across windows and linux without needing to maintain separate enviroment variables in script. However, clayasaurus mentioned in another post that build response files do not currently work on Linux, so I will likely ditch them and just use environment variables instead.

Please post any comments/suggestions/issues on the new build system in this thread. If I hear nothing bad in the next few days, I'll move on to the next task (finishing the documentation).

Oh, and I almost forgot. I no longer have my newbie Linux programming guide to study for shell scripting (I can't believe I lost that friggin book, it was a good one), so I will need to do some research to learn my way around bsh. If anyone else is interested in tackling the Linux build scripts before I get to it, be my guest.

One more thing, if you wish to delete all of the libraries from the \lib subdir for whatever reason, just run cleanlib.bat. I am also considering an install.bat which will allow you to copy all source and library files to different directories. Perhaps you have a \d_lib directory for all of your 3rd party libraries, and a \d_inc directory for all of your third party source, and both of these are configured in dmd's sc.ini file. It's likely convenient to put all derelict packages under a common derelict directory tree. That's what I do locally, myself.

[Derek Parnell]

[aldacron]

[Derek Parnell]

[clayasaurus]

Or my ignorance and/or poor choice of wording. I didn't know there was a difference between builds response file and dmd's response file, having used neither myself. I just remembered from way back that build would complain if I didn't use -Rn.

BTW: I think the following link may be a good reference for the linux shell.

http://www.freeos.com/guides/lsst/

[aldacron]

Cool, then I don't have to change anything and Derek doesn't have to fix any bugs And thanks for the link, Clay.