23 years agodavid_turner committed change 1048 into formatting | ||
Add a comment | ||
24 years agodavid_turner committed change 789 into fixed a bug in "evaluate_rule" where using an undefined variable named in an indirect rule invokation caused a Jam crash.. | ||
24 years agodavid_turner committed change 773 into fixed small typo in comment | ||
24 years agodavid_turner committed change 772 into | ||
24 years agodavid_turner committed change 714 into updated the build system to run correctly on Unix systems | ||
24 years agodavid_turner committed change 713 into updating the build system, documentation, etc.. for the 2.3.5 release | ||
24 years agodavid_turner committed change 712 into adding missing file . Do'h | ||
24 years agodavid_turner committed change 711 into important updates to the Jam build system: - builds easily on Unix systems - specific Makefiles for... Visual C++ and Borland C++ in the "builds" directory. More to come.. - the "jam package" command can be launched once the jam executable was generated on Windows and OS/2 systems in order to build pre-compiled binary packages (simple zip files, no installer)) added a new built-in named FAIL_EXPECTED. See the page http://www.freetype.org/jam/changes.html for more details on this.. « | ||
24 years agodavid_turner committed change 679 into experimental support for wider MAXLINE values on Windows NT (NT 3.51 is detected at run-time in "execnt.c" and dealt accordingly). | ||
24 years agodavid_turner committed change 678 into implementation of a new experimental builtin rule named FAIL_EXPECTED. It is used to indicate that the result of a specific target build action shoul...d be inverted !! this is useful for certain test runs, where a compilation error might need to be interpreted as succesful (and likewise, a clean compile should be seen as an error). Example: FAIL_EXPECTED test$(SUFOBJ) ; « | ||
24 years agodavid_turner committed change 677 into | ||
24 years agodavid_turner committed change 676 into fixing a bug in the identation used to dump debug output | ||
24 years agodavid_turner committed change 675 into fixing original Makefile/Jamfile to run on Unix systems where the current directory isn't in the path | ||
24 years agodavid_turner committed change 640 into Allowed indirect rule invocations of the form: [ $(RULE) param1 : param2 ] this is needed by the Boost build system | ||
24 years agodavid_turner committed change 629 into formatting, and making the Borland C++ default C flags more restrictive (previously, all warnings were disabled) | ||
24 years agodavid_turner committed change 622 into simple change to the README | ||
24 years agodavid_turner committed change 621 into Win 9x related fixed submitted by Fabio Parodi | ||
24 years agodavid_turner committed change 618 into | ||
24 years agodavid_turner committed change 600 into fixed Jamfile for new supported toolsets | ||
24 years agodavid_turner committed change 599 into Adding/Upgrading support for Windows compilers: Visual C/C++ Intel C/C++ Win32-LCC Watcom C/C++ Borland C/C++ ... MingW (gcc without cygwin) Adding support for new compilers on OS/2: Watcom C/C++ EMX-GCC Note that there is a new scheme to select the compiler you want to use on a given platform: - define one of the following environment variable, with the appropriate value according to this list: Variable Toolset Description BORLANDC Borland C++ BC++ install path VISUALC Microsoft Visual C++ VC++ install path VISUALC16 Microsoft Visual C++ 16 bit VC++ 16 bit install INTELC Intel C/C++ IC++ install path WATCOM Watcom C/C++ Watcom install path MINGW MinGW (gcc) MinGW install path LCC Win32-LCC LCC-Win32 install path - define the JAM_TOOLSET environment variable with the *name* of the toolset variable you want to use. e.g.: set VISUALC=C:\Visual6 set JAM_TOOLSET=VISUALC if Jam is invoked with no JAM_TOOLSET defined, it will print a table of valid values and their expected meaning.. « | ||
24 years agodavid_turner committed change 598 into | ||
24 years agodavid_turner committed change 597 into Adding support for Windows 95/98 through a specific implementation of the "exec" module, named "execnt.c" | ||
24 years agodavid_turner committed change 595 into Adding support for the new HDRMACRO builtin. The latter is used to specify a file containing macro definitions that are later used in #include statem...ents, as in: #include MYFILE_H A line like: HDRMACRO mydefs.h ; will parse the file "mydefs.h" for lines of the form: #define MACRO <.......> and #define MACRO "......." and will store their definition in a global dictionary. When a line like #include MACRO is later found during header file processing, the macro will be resolved accordingly.. « | ||
24 years agodavid_turner committed change 594 into | ||
24 years agodavid_turner committed change 591 into This branch contains some improvements made to Jam for the FreeType 2 project: | ||
Adjust when notifications are sent to you about reviews that you're associated with (as an author, reviewer, project member or moderator).