On 4/3/2012 04:06, Mattias Gaertner wrote:
On Mon, 02 Apr 2012 22:36:23 -0400
waldo kitty<wkitt...@windstream.net> wrote:
[...]
i don't know why it cannot overwrite C:\freepascal\laz\lazarus.exe... and
actually, is it supposed to be compiling lazarus after a svn update when we
haven't yet specifically (re)built lazbuild which is the next step in the script
i've been working on? after that, we do the lazbuild command thing to actually
build lazarus... i'm kinda confused :?
"make all" builds a default IDE.
ahhh... "default" has a different meaning in this case? not the same "default"
as the lazbuild (or profiles??) default??
Yes, there is the default IDE and the default profile.
Your default profile includes your installed packages so it may fail.
"make clean all" builds a default IDE. This way users have a simple way
to get a working IDE.
ok...
stripping all the fancy out, here's my script in its rawest form and a few
questions...
1. "cleanbigide" before svn update and again building lazbuild?
"make clean" is enough. cleanbigide now simply executes clean.
for both before the svnupdate and when building lazbuild??
Once is enough.
2. is "clean all" really needed after the svn update in this script?
Yes, if it should be stable.
No, if you want the optimal way, that means building only those things
you need.
hummm... i was thinking about asking if there was something like maybe "make
tools" that would only build the tools instead of also trying to build
lazarus... the way my script is written, it doesn't make sense to build lazarus
and then turn around and build it again... what am i missing?
Yes, "make all" calls "make tools". And "make starter" and some more.
And maybe we have to add a further item.
You have the choice to use the simple but somewhat inefficient "make
all"
that's what i'm using for now... see script below...
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 :?
where/how can one get a list of the targets and what they do?
but it would be nice to be able to follow... i mean, really... since "make all"
builds lazbuild, i don't need to specifically do that any more as we were a few
weeks back... a default lazarus.exe is ok, too... i can save that off to a back
up name and still build the rest... i think i'm seeing that the lazbuild version
of lazarus will also need to be renamed or copied to lazarus.exe... anyway,
here's my (unbeautified) script now...
========== snip ==========
[trim var setting stuff]
cd %myLAZpath%
make clean
if errorlevel 1 goto error
TortoiseProc /command:update /path:"%myLAZpath%"
cd %myLAZpath%
make all
if errorlevel 1 goto error
copy lazarus.exe lazarus.default.exe
cd %myLAZpath%
lazbuild.exe --build-ide="-vut" --build-mode="debug ide"
if errorlevel 1 goto error
copy lazarus.new.exe lazarus.exe
copy lazarus.new.exe lazarus-debug.exe
goto end
:error
echo.
echo ***************************************************************************
echo * ERROR * ERROR * ERROR * ERROR * ERROR * ERROR * ERROR * ERROR * ERROR *
echo ***************************************************************************
echo.
goto end
:end
echo %0 execution complete!
========== snip ==========
i'll be removing the "-vut" from the build-ide shortly... question... are these
two the same?
--build-ide=
--build-ide=""
i'm looking at the possibility of passing parameters to the script on the
command line for use deeper in the processing... like adding -vut to lazbuild
and maybe even in the default "make all" ???
--
_______________________________________________
Lazarus mailing list
Lazarus@lists.lazarus.freepascal.org
http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
