Re: [ptxdist] regression linking against libcgi after fixing patches in a53b663
Hei hei, Am 2012-10-28 18:09, schrieb Michael Olbrich: I'm not familiar with autotools to fix this myself. Expected behaviour would be some libcgi.so.x.y.z is installed and libcgi.so.x and libcgi.so are symlinks of which only libcgi.so.x is installed to the target. If I rename libcgi.so on my target to libcgi.so.0.0.0 and create a symlink libcgi.so.0 my cgis work again. I think I fixed this now, but I can't test it. Please try. Works now. File is libcgi.so.0 and symlink is libcgi.so pointing to the file. That sounds good. Especially the part about a release. I always like it when I can remove patches from ptxdist. If someone is actually working on this, I really suggest cleaning up the build system. If you don't know enough about this, then look at libabc[1]. This is a good place to get started with this. Okay I'll try to get a release out, we'll see. [1] http://0pointer.de/blog/projects/libabc.html I will have a look at this, thank you. (Had already forgotten I stumbled over libabc a long while ago.) Greets Alex -- »With the first link, the chain is forged. The first speech censured, the first thought forbidden, the first freedom denied, chains us all irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie) *** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 *** -- ptxdist mailing list ptxdist@pengutronix.de
[ptxdist] UBIFS generation question
Hi, I currently add the git commit to my BSP by adding this to a custom overlay rule. echo $(shell git rev-parse --verify HEAD) $(ROOTDIR)/etc/revision That works fine for creating the file in the platform/root directory. When I started to use the UBI image I noticed that file was missing from my root filesystem. I see that the ubi.make script does a targetinstall to platform/images/working_dir and then generates the UBI image from there. Which obviously does not have my revision. How can I fix/modify my line above so it makes it into both the root directory and the UBI image. I'm on ptxdist-2011.07.0 Thanks in advance, Jeff -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] UBIFS generation question
Hei Jeff, On 01.11.2012 19:22, Jeff Horn wrote: echo $(shell git rev-parse --verify HEAD) $(ROOTDIR)/etc/revision I personally use `git describe --tags` for this, but that's more a question of taste. That works fine for creating the file in the platform/root directory. When I started to use the UBI image I noticed that file was missing from my root filesystem. I see that the ubi.make script does a targetinstall to platform/images/working_dir and then generates the UBI image from there. Which obviously does not have my revision. How can I fix/modify my line above so it makes it into both the root directory and the UBI image. What about creating the file in projectroot/etc/revision, putting a placeholder e.g. @REVISION@ in it and using something like this in your rule: @$(call install_alternative, somepackage, 0, 0, 0644, \ /etc/revision) @$(call install_replace, somepackage, /etc/revision, \ @REVISION@, $(shell git rev-pares --verify HEAD) ) Like this the file gets in the package file and should be installed in the UBI image. We have a similar approach working in our BSP. Greets Alex signature.asc Description: OpenPGP digital signature -- ptxdist mailing list ptxdist@pengutronix.de
Re: [ptxdist] UBIFS generation question
Thanks Alex, I have it all working now. Jeff On Thu, Nov 1, 2012 at 1:37 PM, Alexander Dahl p...@lespocky.de wrote: Hei Jeff, On 01.11.2012 19:22, Jeff Horn wrote: echo $(shell git rev-parse --verify HEAD) $(ROOTDIR)/etc/revision I personally use `git describe --tags` for this, but that's more a question of taste. That works fine for creating the file in the platform/root directory. When I started to use the UBI image I noticed that file was missing from my root filesystem. I see that the ubi.make script does a targetinstall to platform/images/working_dir and then generates the UBI image from there. Which obviously does not have my revision. How can I fix/modify my line above so it makes it into both the root directory and the UBI image. What about creating the file in projectroot/etc/revision, putting a placeholder e.g. @REVISION@ in it and using something like this in your rule: @$(call install_alternative, somepackage, 0, 0, 0644, \ /etc/revision) @$(call install_replace, somepackage, /etc/revision, \ @REVISION@, $(shell git rev-pares --verify HEAD) ) Like this the file gets in the package file and should be installed in the UBI image. We have a similar approach working in our BSP. Greets Alex -- ptxdist mailing list ptxdist@pengutronix.de -- ptxdist mailing list ptxdist@pengutronix.de
