On 4/3/2012 14:52, waldo kitty wrote:
On 4/3/2012 04:06, Mattias Gaertner wrote:
or you can hand craft your own command, but then you have to
follow the development of the Makefiles.
hummm... i tried following thru them trying to find the reason for some echo
lines after building apiwizz but failed miserably... make stuff is not my forte
:?
here's what i spoke of when i wrote "echo lines after building apiwizz" above...
lines 2127 and 2128 below...
2115 make[3]: Entering directory `C:/freepascal/laz/tools/apiwizz'
2116 c:/freepascal/fpc/2.4.5/bin/i386-win32/ppc386.exe -gl -Fu.
-Fu../../lcl/units/i386-win32 -Fu../../components/lazutils/lib/i386-win32
-Fu../../lcl/units/i386-win32/win32 -FE. -FU. -di386 apiwizz.pp
2117 Free Pascal Compiler version 2.4.5 [2011/06/01] for i386
2118 Copyright (c) 1993-2010 by Florian Klaempfl
2119 Target OS: Win32 for i386
2120 Compiling apiwizz.pp
2121 Compiling apiwizard.pp
2122 Compiling resource .\apiwizz.or
2123 Linking .\apiwizz.exe
2124 1019 lines compiled, 5.3 sec , 1345664 bytes code, 352104 bytes data
2125 make[3]: Leaving directory `C:/freepascal/laz/tools/apiwizz'
2126 make[2]: Leaving directory `C:/freepascal/laz/tools/apiwizz'
2127 echo
2128 ECHO is off.
2129 make --assume-new=lazres.pp lazres.exe
i suspect that this is coming from tools\Makefile and/or tools\Makefile.fpc off
of the lazarus directory... i searched for "lazres.pp" in makefile* and these
two are the only ones that turned up...
i suspect that some desired output may be being lost... namely that of
$(LAZARUS_LIBPATHS) which is only set of the $(OS_TARGET) is darwin... with
$(LAZARUS_LIBPATHS) being undefined, it also explains the extra space in the
compile line (#2116 above) right after the "-gl" entry... this is seen in
tools\Makefile on all the compiler options lines for all of the different OS
make targets...
--
_______________________________________________
Lazarus mailing list
[email protected]
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
