FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Release Announcements
Goto page Previous  1, 2
 
Post new topic   This topic is locked: you cannot edit posts or make replies.     Forum Index -> Build
View previous topic :: View next topic  
Author Message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Thu Apr 28, 2005 6:21 pm    Post subject: Re: Release Announcements Reply with quote

v2.03 changes
** FIX: thanks to Carlos: The linux build had a spelling mistake in source.d (line 286). The indentifier "lNextMod" should have been coded as "lNextModule".
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Sun May 01, 2005 10:35 pm    Post subject: Re: Release Announcements Reply with quote

v2.04 changes
** FIX: thanks to Nils Hensel: The utility was not correctly parsing the DFLAGS line in the configuration file when it contained embedded quote characters.
** FIX: thanks to Anders F Bjoerklund: The utility was not treating directory names that contained dots correctly.
** FIX: thanks to Carlos: Unix-style files that end with a nested comment delimiter are now handled correctly.
** ENH: thanks to qbert(Charlie) : The location of the librarian tool can now be specified. It can be explictly named on a LIBCMD= line inside the DMD configuration file, or failing that, implictly assumed to be in the same directory as the DMD linker.
** ENH: A new commandline switch -LIBOPT which allows you to pass commandline options to the librarian.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Wed May 04, 2005 4:49 am    Post subject: Re: Release Announcements Reply with quote

v2.05 changes
** FIX: When supplying some forms of relative paths, the utility would crash or give the wrong canonical form of the path. This effected formats like \..\anything and C:..\anything
** FIX: The utility now assumes the current directory if it can not locate the compiler using the paths on the system PATH symbol.
** FIX: The utility now assumes the compiler's location if no path for the configuration file has been specified.
** FIX: The utility now supports better parsing of the lines in the configuration file. It handles odd variations of embedded quotes.
** ENH: The utility now supports Windows 95/98/ME for file times.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Sat May 07, 2005 7:52 am    Post subject: Re: Release Announcements Reply with quote

v2.06 changes
** FIX: thanks to phoenix: When emitting commandline parameters for the compiler or librarian, it was possible to have some ending with \" which caused the shell to escape the quote character and thus provide incorrect parameters to the compiler.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Sun May 29, 2005 7:35 pm    Post subject: Re: Release Announcements Reply with quote

v2.07 changes

** ENH: New switch -nodef to prevent the utility from automatically creating a Module Definition File (.def)

** ENH: You can now specify default, and special, settings for the utility's command line. These are placed in a text configuration file called build.cfg. The utility first looks in the same directory as the utility's executable for the configuration file. After processing any configuration file found there, it then looks in the same directory as the compiler for a configuration file (build.cfg) and processes it if found.

** ENH: To support special command line settings that may be specified in the utility's configuration file(s), you can indicate one or more setting groups on the command line. These take the format of +groupname. The configuration file(s) are scanned for special group settings after the default ones have been processed.

** ENH: To remove an earlier specified command line switch, you can prepend it with a hyphen. This new feature may be needed when command line switches can come from multiple sources (the original command line, utility response files, and utility configuration files), and you need to remove a switch that may have been provided by some other source.
For example to negate an earlier "-unittest" switch you code add "--unittest" to the command line.

** ENH: New switch -od is used to nominate a directory for temporary files. For the DigitalMars compiler, this also is used as the location to create object files.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Tue Aug 09, 2005 6:18 pm    Post subject: Re: Release Announcements Reply with quote

v2.08 changes
** FIX: thanks to teqdruid: In Unix environments, any pragma(link, <name>) statements were not sending the correct syntax to the compiler's command line. The "<name>" is now prefixed with "-L-l" for Unix systems.

** FIX: thanks to Carlos: In Unix environments, any "-version" switch on the Utility's command line was not being converted to the correct Unix format of "-fversion...". So now, if the Build tool gets either "-version..." or "-fversion=..." on its command line, it will recognise it as a 'Version' request for the compiler and output it on the command line in the correct format for the environment it is running in, namely "-fversion..." for GNU (gdc) and "-version..." for Windows.
Note: The same applies to the "-debug..." and "-fdebug..." switches.

** FIX: The pragma(nolink) was being ignored under some circumstances. Now it splits the compilation phase from the linking phase and excludes the 'nolink' files from the linker's command line.

** FIX: thanks to kris: 'debug' statements were not being taken into account when examining code for import statements.

** FIX: 'debug' and 'version' levels are now being taken into account.

** FIX: 'debug' and 'version' values being set inside a source file were being made global rather than module scoped.

** FIX: thanks to carlos: The utility was not processing the -I switch correctly when using GDC compiler.

** ENH: The utility can now accept the -I switch in two forms: -I<path> and -I <path> on its command line, regardless of which compiler is being used. When invoking the compiler, it uses the correct format on the command line of the compiler being used, namely "-I<path>" to DMD compiler and "-I <path>" to GDC.

** ENH: The path of any source file that imports a module will be added to the list of root paths to search for module source files. This means that you can now have module source files referenced relative to the source file that imports them. This is the new default behaviour but it can be turned off by using the new -noautoimport switch or for individual files by placing them inside parenthesis.

** ENH: New switch -noautoimport is used to turn off the automatic adding of search roots based on the path of the source files being compiled.

** ENH: New switch -LIBPATH= is used to add search paths for library files.

** WARN: The utility only does a single scan of each source file and thus if any file sets a 'debug' or 'version' value after a function which uses that value, it will be ignored. You are requested to ensure that all your 'debug' and 'version' setting is done prior to the first module member.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Thu Apr 06, 2006 9:29 am    Post subject: Re: Release Announcements Reply with quote

Release 2.09 (build #1197) is now available 10 Aug 2005
URL: Build Project Home

v2.09 changes
** FIX: thanks to barrett9h (rodolfo): Now correctly handles the return value from Unix system() call.
** FIX: thanks to oniony: Now handles non_ASCII characters in PATH environment symbol.
** CHG: The "-silent" switch now also hides the linker stdout display.
** CHG: Now supports and requires DMD v0.126 and GDC v0.13 or later.
** ENH: New pragma(export_version) allows specified version identifiers to be passed to all modules being compiled.
** ENH: New command line switch "-run" to run the program after a successful link.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Mon Jun 05, 2006 11:33 pm    Post subject: Re: Release Announcements Reply with quote

v2.10 changes
FIX: The default Build Response File invoked when just placing '@' on the command line is now correctly named "build.brf"
ENH: For Windows environments, command line files can now use either "/" or "\" as path separator characters.
ENH: The linker program is now used directly rather than being invoked via DMD.
ENH: You can now specify the default linker switches in the Build Configuration File.
ENH: Using the new switch -PP , you can now specify additional paths to search for files.
ENH: Support for Ddoc files.
CHG: The files are now compiled and linked in the same order that they are scanned in. Previously the order depended on the hashing algorithm of D's associative array implementation and the names of the directories containing the source files.
CHG: The "-run" switch renamed to "-exec" to avoid clashing with dmd.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Fri Jun 09, 2006 1:19 am    Post subject: Re: Release Announcements Reply with quote

v3.00 changes
** FIX: Build was using the wrong object file during linkages if a target object file did not exist but one with the same name existed in any of the Import paths.
** FIX: With the -R=No switch, when using the Digital Mars linker, Build was not formatting the command line correctly.
** FIX: Ticket #10 The tool now recognises the pragma linked object files when building a library.
** FIX: Ticket #9 Now, if the output file created by the rule ends with the library extention, it is presented to the linker as a library rather than an object file.
** FIX: thanks to gmiller: Added booltype.d to Makefile files.
** FIX: Ticket #15 GDC places object files in the directory from which it is called so the tool no longer assumes the same directory as the corresponding source file.
** FIX: Ticket #17 Hopefully its a more posix-friendly tool now. Most of the hard-coded switches and options that are environment related are now user-configurable via the Configuration File functionality.
** FIX: thanks to gmiller: Corrected the imports in util.fileex.d
** FIX: thanks to gmiller: Module and package exclusion was not working if your current directory was in a directory tree that contained the module/package you were excluding. For example if your current directory was C:\dmd\src\phobos it would not exclude any of the 'std' modules.
** ENH: Any file name on the command line with an extention of ".brf" will be used as a Build Response File
** ENH: If there is nothing on the command line and the file 'build.brf' exists in the current directory, then it will be used as the Build Response File for this run.
** ENH: Will now look for the compiler's configuration file in the following areas...

    * If defined, the directory defined by the ConfigPath configuration item in Build's configuration file. And in this case it doesn't look anywhere in any of the areas listed below.
    * The current directory.
    * The directory named in the HOME environment symbol.
    * For Windows environments only, the directory named in the combination of the HOMEDRIVE and HOMEPATH environment symbols.
    * The same directory in which the compiler resides.
    * The directory defined by the EtcPath configuration item in Build's configuration file.

** ENH: It is now possible to add environment specific items to the build.cfg file. To do so, add the items to the appropriate item group...
Code:

    [Windows]
    # items that only apply when building in Windows.

    [Posix]
    # items that only apply when building in Posix (unix).

    [DigitalMars]
    # items that only apply when building with DigitalMars tools.

    [GNU]
    # items that only apply when building with GNU tools.

    [Windows:DigitalMars]
    # items that only apply when building with DigitalMars tools in Windows.

    [Windows:GNU]
    # items that only apply when building with GNU tools in Windows.

    [Posix:DigitalMars]
    # items that only apply when building with DigitalMars tools in Posix.

    [Posix:GNU]
    # items that only apply when building with GNU tools in Posix.

** ENH: A new switch, -UMB=<( Yes/No)> is used to specify where the linker expects the object files to be. Unless this switch is used the linker is assumed to look for the object files in the same directory as the source files. However if the linker that you use expects them to be all in the current directory, you can use -UMB=yes to ensure that the compiler places object files in the current directory.
** ENH: A new switch, -modules=<( name)> is used create a Module List File.
** CHG: When building the Build application itself, you must now add -version=BuildVerbose to the command line if you want an edition of Build that supports the -V (verbose) switch. As shipped, the pre-built editions of Build do not support the -V switch.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Fri Jun 23, 2006 9:17 pm    Post subject: Re: Release Announcements Reply with quote

v3.01 changes
** FIX: Ticket #18 The tool now ignores duplicate source file names supplied to it from anywhere.
** FIX: Ticket #19 The tool now only passes object files, library files, DigitalMars .def files, and resource files to the linker.
** FIX: Ticket #20 The 'Rules' system can now handle creation of D source files.
** FIX: Ticket #22 A few spelling errors corrected in the documentation.
** FIX: Ticket #23 When using a response file for the DigitalMars linker, the tool now makes provision for Resource Files.
** FIX: Ticket #24 The tool now recognises .di files as source files for the purposes of determining dependancies, but does not allow them to be presented on the DMD compiler's command line.
** FIX: Ticket #25 The tool now scans the PATH environment symbol rather than assuming that supplie executable file names that do not have a path are in the current directory.
** FIX: Ticket #26 The LINKCMD configuration item is now corrected parsed.
** ENH: The 'Rules' functionality now allows some new special tokens that represent the Basename and Path of the input and output files.
** ENH: The 'Rules' functionality now ensures that the output file's path exists prior to running the Rule's tool application.
** ENH: The LINKCMD is now able to be used in the Build configuration file.
** ENH: A new switch "-uses" will cause the tool to create a cross-reference file that details what modules use what, and what modules are used by other modules.[/quote]
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Wed Sep 20, 2006 8:13 pm    Post subject: Re: Release Announcements Reply with quote

Release 3.02 (build #2208) is now available 23 Jun 2006
URL: Build Project Home

v3.02 changes
FIX: Ticket #27 When using 'gcc' as the linker tool, Build now uses a space character to delimit file names.
FIX: Ticket #28 The Optlink switch options are now correctly placed in a response file
FIX: Ticket #29 The -exec now works correctly.
FIX: Ticket #32 The Windows executable in the distro now updates the auto_build_number.
ENH: Ticket #30 The Rules subsystem can now be used to generate D source code. There are number of changes in this area so read the rules documentation and pragma documentation for details.
ENH: Ticket #31 It is now possible to stop a source file from being compiled. A new "pragma(ignore)" has been implemented.
ENH: There are some new configuration items that can be used to adjust the tools usage. Have a look at the example configuration file in the distrubution package.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Derek Parnell



Joined: 22 Apr 2004
Posts: 408
Location: Melbourne, Australia

PostPosted: Sun Oct 15, 2006 10:14 pm    Post subject: Re: Release Announcements Reply with quote

Release 3.03 (build #2371) is now available 20 Sep 2006
URL: Build Project Home

** FIX: Ticket #33 For unix editions, 'pthread' is now a default library, '-g' is used instead of '/co' to generate debug data, '-o ' is used instead of '-of', and spaces are placed in between consecutive '-L' switches. Note that if you want to place library files on the command line, you still have to include the '.a' file suffix.
** FIX: Ticket #34 For GNU, 'gdc' is the default linker, the library switch is now '-L-l', 'gphobos' is used instead of 'phobos', and the makefile includes the '-version=BuildVerbose' switch.
** FIX: Ticket #35 It is now possible to use relative paths on the command line files.
** FIX If you use the '-od' switch then the '-op' switch is not used.
** CHG: Ticket #36 The default name for the executable is now 'bud', but you can change it to anything you like.
** CHG: Ticket #37 Changed defaults to support GDC out-of-the-box.
** ENH The utility now also checks for a '[darwin]' section in the Configuration File.
** ENH The utility now supports the import syntax that was introduced with DMD v0.163.
** ENH The distribution now includes example configuration files for a number of environments.
** ENH The Configuration File now supports a new FINAL command that allows you to run jobs after a successful build.
_________________
--
Derek
skype name: derek.j.parnell
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic   This topic is locked: you cannot edit posts or make replies.     Forum Index -> Build All times are GMT - 6 Hours
Goto page Previous  1, 2
Page 2 of 2

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group