|
From: Oliver N. <dig...@gm...> - 2008-06-12 12:30:08
|
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I have a small question about the buildsystem for DL-1.3.x. I added some small packages for my custom-cd. The build of these packages went normal, but i had some errors in the install part of my scripts... The question is: When i change something in the scripts (eg. in the install path) do i have to restart 'make prepare' always? ( takes relatively long time!) Or is there another way to tell the system that a script changed? Thanks, Olli -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with CentOS - http://enigmail.mozdev.org iD8DBQFIURbB724ZL5LNhNcRAvPvAJ95Nn5Vtgr6H59d6y4B984X91fC0wCfazmi xHpTgv9Vs8NfVwvthIl3SdI= =PFfZ -----END PGP SIGNATURE----- |
|
From: Heiko Z. <he...@zu...> - 2008-06-12 19:47:54
|
Quoting Oliver Niesner <dig...@gm...>: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi! > > I have a small question about the buildsystem for DL-1.3.x. > I added some small packages for my custom-cd. > The build of these packages went normal, but i had some errors in > the install part of > my scripts... > > The question is: > When i change something in the scripts (eg. in the install path) do > i have to restart > 'make prepare' always? ( takes relatively long time!) > Or is there another way to tell the system that a script changed? The only thing you have to do is to delete the appropriate .done_XXX_YYY file in build/tmp/. XXX is either build, install or iso YYY is the name of the script then you can do again a "make makefile" or "make build install iso" -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |
|
From: Oliver N. <dig...@gm...> - 2008-06-12 20:50:44
|
> The only thing you have to do is to delete the appropriate > .done_XXX_YYY file in build/tmp/. > XXX is either build, install or iso > YYY is the name of the script > > then you can do again a "make makefile" or "make build install iso" > Hmm, i did it exactly like you mentioned, but it seems that changes aren't recognized in all cases :-| I changed for example the install path of my build script, cause i missed something. First i made a make clean Then i deleted build/tmp/.done_build_foo After that i typed 'make makefile' I could see that the build part passed without errors, but the install part wasn't executed at all! No build/tmp/.done_install_foo file exists! Without any further changes in the script i tried a 'make prepare' After that a 'make makefile' compiled my stuff AND the install part was executed and the .done_install_foo file was in /tmp/ That was the reason i asked if there is another mechanism to change the build/install behavior. It's not that big problem everything is working now - i just asked because it is more likely that i missed something and you already know ;-) Thanks, Olli |
|
From: Heiko Z. <he...@zu...> - 2008-06-13 13:00:33
|
Hey, I think the 'install' link in build/.buildorder was missing, that's why you had to run prepare. One thing prepare does is calculate the run-order of the scripts. If you did changes to the top section of the build script, the one which controls the dependencies, then you can't get around running make prepare. Heiko Quoting Oliver Niesner <dig...@gm...>: > >> The only thing you have to do is to delete the appropriate >> .done_XXX_YYY file in build/tmp/. >> XXX is either build, install or iso >> YYY is the name of the script >> >> then you can do again a "make makefile" or "make build install iso" >> > > Hmm, i did it exactly like you mentioned, but it seems that changes > aren't recognized in all cases :-| > I changed for example the install path of my build script, cause i > missed something. > First i made a make clean > Then i deleted build/tmp/.done_build_foo > After that i typed 'make makefile' > I could see that the build part passed without errors, but the install > part wasn't executed at all! > No build/tmp/.done_install_foo file exists! > Without any further changes in the script i tried a 'make prepare' > After that a 'make makefile' compiled my stuff AND the install part was > executed and the .done_install_foo file was in /tmp/ > > That was the reason i asked if there is another mechanism to change the > build/install behavior. > > It's not that big problem everything is working now - i just asked > because it is more likely that i missed something and you already know ;-) > > Thanks, > > Olli > > > > > > > > > ------------------------------------------------------------------------- > Check out the new SourceForge.net Marketplace. > It's the best place to buy or sell services for > just about anything Open Source. > http://sourceforge.net/services/buy/index.php > _______________________________________________ > Devil-linux-discuss mailing list > Dev...@li... > https://lists.sourceforge.net/lists/listinfo/devil-linux-discuss > -- Regards Heiko Zuerker http://www.devil-linux.org ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. |