OESF | ELSI | pdaXrom | OpenZaurus | Zaurus Themes | Community Links | Ibiblio

IPB

Welcome Guest ( Log In | Register )

> Extending Dev_img With Additional Headers And Libs, Howto do this
andrewmaier
post Mar 10 2005, 01:58 AM
Post #1





Group: Members
Posts: 26
Joined: 8-February 04
Member No.: 370



Hi,

I am using the dev_img for compiling and packageing some software for my Z. I am very happy with it, since my attempts to crosscompile have never really been very successfull.

Yet I am now facing the problem, that naturally the dev_img cannot contain rverything I need for compiling certain software packages. E.g. openssl and Berkeley DB are missing.

So how do I extend the dev_img in an intelligent way, that is not to unpack the thing and repack it again with my extensions? Or can I simply mount the image rw and add the stuff I want? CRAMfs does not allow you to do this. Is squashfs different?

For the Berkeley DB I simply made a dev ipk and installed it, but this will get annoying over time, so I am sure there should be solution which is more intelligent.

How do other people solve this?


Andrew,
who is close to having a full chain of an imap-based mail solution, using mutt, ssmtp for mail, rlpr and a2ps for printing
Go to the top of the page
 
+Quote Post
 
Start new topic
Replies
ashikase
post Mar 10 2005, 04:59 PM
Post #2





Group: Members
Posts: 280
Joined: 17-March 04
From: Osaka, Japan
Member No.: 2,375



The symlinking to /usr/local/include is really annoying; if /usr/local/include already exists, the link is created as /usr/local/include/include (>_<)

Everytime I install a new rom and resetup the dev image, I have to cleanup after it. Hopefully if another dev image is released, this will be fixed.

One additional thing... I've never really thought about it, but does anyone know why the dev image needs to create directories/links (automake, develop, letc.) in the /home/zaurus directory, and then further links in bin/lib/include? Why not just link directly from bin/lib/include to the mount location?

- ashikase
- anpachi, gifu, japan
Go to the top of the page
 
+Quote Post
Stubear
post Mar 10 2005, 06:26 PM
Post #3





Group: Members
Posts: 1,164
Joined: 17-December 03
From: Melbourne, AUSTRALIA
Member No.: 1,219



QUOTE(ashikase @ Mar 11 2005, 09:59 AM)
The symlinking to /usr/local/include is really annoying; if /usr/local/include already exists, the link is created as /usr/local/include/include (>_<)

Everytime I install a new rom and resetup the dev image, I have to cleanup after it. Hopefully if another dev image is released, this will be fixed.

One additional thing... I've never really thought about it, but does anyone know why the dev image needs to create directories/links (automake, develop, letc.) in the /home/zaurus directory, and then further links in bin/lib/include? Why not just link directly from bin/lib/include to the mount location?

- ashikase
- anpachi, gifu, japan
*


Yeah,

I think I'll send Anton a patch of the changes I made to the compiler setup script.

I've been wondering about all the links in /home/zaurus too. I first thought that develop was so that you could easily add source packages into develop/src and didn't need to cd far from $HOME, but $HOME/develop/src is read-only sad.gif

THe other links had me confused too

Stu
Go to the top of the page
 
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 21st November 2014 - 08:39 AM