On Mon, 21 Feb 2005 08:03:09 +0100, Anders F Björklund wrote:

> John Reimer wrote:
> 
>> I really see no point in the way you've been criticising the source code, Anders. The build tool is an open project.  Derek contributed a hefty amount of work/time to get it out there for the rest of us to play with.
> 
> Sorry, it was all just meant as constructive criticism...

It was, even though the tone might have been a bit strong for some.

>> If you don't like the style, change it to the way you like it for your own personal use.  "build" is still a proof-of-concept, I think.  It's an example of what a build tool for D can evolve into.
> 
> Yeah, that was why I tried to port it to GDC and Darwin ?

Thanks for doing that. Does my ...

  version(darwin) version = Posix;
  version(linux) version = Posix;

idea work for you?

>> If it gets on as a project on dsource.org where more than one person can contribute, perhaps that's the time to discuss coding style.
>> 
>> But until then, it's probably not wise to discourage new contributions with such pettiness.
> 
> Too used to working on community projects, I suppose. http://c2.com/cgi/wiki?CollectiveCodeOwnership

I'm also used to working with project teams, both small and largish (60+
people).

> Hope that Derek wasn't too put off or discouraged...

Not at all. I've already added your patches. I've removed all those instances of superfluous semi-colons and removed the 'redundant' aliases.

I'm preparing to start this up as a DSOURCE.ORG project.

> I just happen to think that how code looks is important.

And so do I, that's why I deliberately inserted all those semi-colons and aliases in the first place ;-)

-- 
Derek
Melbourne, Australia
21/02/2005 6:13:16 PM

Derek Parnell wrote:

>>Sorry, it was all just meant as constructive criticism...
> 
> It was, even though the tone might have been a bit strong for some.

Just consider it a Swedish personality trait, not ignorance :-)

(English is not my native language, as with a lot of people here)

>   version(darwin) version = Posix;
>   version(linux) version = Posix;
> 
> idea work for you?

It's part of a bigger problem, and needs a more permanent change...

It kinda works, just that a) it needs to be repeated in every single
project and b) the code imports and uses std.c.linux.linux module
(which needs to be changed into std.c.darwin.darwin, for instance)

But it's a different discussion...
(and Mac OS X is not a supported DMD platform, it's just a GDC one)

>>Hope that Derek wasn't too put off or discouraged...
> 
> Not at all. I've already added your patches. I've removed all those
> instances of superfluous semi-colons and removed the 'redundant' aliases. 

Ok, hope I'm not "cramping your style" here or anything ?
Maybe it is my code that needs adapting to local customs.

> And so do I, that's why I deliberately inserted all those semi-colons and
> aliases in the first place ;-)

:-)

--anders

Hello,

i can't find the build programm. Have you change the url?

mfg Manfred

Am Sun, 13 Feb 2005 01:21:56 +1100 schrieb Derek:

> The source code is now available for the build utility I've been working on.
> 
>   http://www.users.bigpond.com/ddparnell/build.zip
> 
> This contains a number of source files, a Windows executable (build.exe), and some files to recompile the application.
> 
> First, extract all the files from the zip into a single directory. To recompile the application, from the command line enter ...
> 
>   dmd @build.rsp
> 
> If you have the compiler in your path and the standard configuration file, this should work just fine. Otherwise you might need to tweak it.
> 
> There are a number of source files in the form "*_bn.d". These are automatically maintained by build so don't edit them. These are automatically incremented build numbers for a module. To get build to maintain a build number file, insert into each module you need it for ...
> 
> private import <modulename>_bn;
> 
> Your code can then access the build number for the module like this ...
> 
>    writefln("Module Build Number %d", auto_build_number);
> 
> 
> To see the command line parameters and switches, just run build without anything else on the command line. You should get something like ...
> 
> Path and Version : F:\Projects\build\build.exe v1.0(115)
> Usage: build sourcefile [options objectfiles libraries]
>   sourcefile D source file
>   -v         Verbose (passed through to D)
>   -V         Verbose (NOT passed through)
>   -DCPATH<path> <path> is where the compiler has been installed.
>              Only needed if the compiler is not in the system's
>              PATH list. Used if you are testing an alternate
>              version of the compiler.
>   -CFPATH<path> <path> is where the D config file has been installed.
>   -full      Causes all source files, except ignored modules,
>               to be compiled.
>   -link      Forces the linker to be called instead of the librarian.
>               (Only needed if the source files do not contain
>                main/WinMain)
>   -nolink    Ensures that the linker is not called.
>               (Only needed if main/WinMain is found in the source
>                files and you do NOT want an executable created.)
>   -lib       Forces the object files to be placed in a library.
>               (Only needed if main/WinMain is found in the source
>                files AND you want it in a library instead of
>                an executable.)
>   -nolib     Ensures that the object files are not used to form
>               a library.
>               (Only needed if main/WinMain is not found in the source
>                files and you do NOT want a library.
>   -allobj    Ensures that all object files are added to a
>               library.
>               (Normally only those in the same directory are added.)
>   -cleanup   Ensures that all object files created during the run
>               are removed at the end of the run, plus other work files.
>   -gui       Forces a GUI application to be created.
>               (Only needed if WinMain is not found in the source files.)
>   -X<module> Modules to ignore (eg. -Xmylib)
>   -M<module> Modules to notice (eg. -Mphobos)
>   [...]      All other options, objectfiles and libraries are
>               passed to the compiler
> 
> 
> The idea of 'build' is to give it the top-level source code file for your application, and it will then work out all the dependencies and which files are need to be recompiled. Typically it is run from a command prompt like ...
> 
>    build myapp
> 
> Which will then create myapp.exe (for Windows) based on the imports
> contained in the related sources.
> 
> If it finds a function called either 'main' or 'WinMain' it will assume you want to create an executable. If it doesn't find this, it assumes you want to create a library.
> 
> If you use the -V switch, you will get a lot of information about the decisions it is making for this run.
> 
> **** NOTE **** This is only version 1.0, and thus will have mistakes in it and some missing functionality. Please let me know about anything that needs improvement. Eventually, I'll get this onto DSource.org as a project and we can then use SVN to manage the source modifications.
> 
> Finally, this tool is useful to me, but that doesn't mean that you will find it useful for yourself. If you don't like it, then don't use it. I won't mind at all.

On Sat, 26 Feb 2005 18:47:37 +0100, Manfred Hansen wrote:

> Hello,
> 
> i can't find the build programm. Have you change the url?
> 
Yes. It is now being hosted by the DSource project.

  http://www.dsource.org/projects/build

It is also at release level v1.5 now and appears fairly stable.

-- 
Derek
Melbourne, Australia