--- In [email protected], Davide Cantaluppi <[EMAIL PROTECTED]> wrote: > > Hi all, > > If the problem is to fit the whole library into the flash, why you have not > considered to put a symbolic link from the flash to /var/your_library and a
That is correct. I'm doing this already for my "normal" application. I have a link "/domotics" which is pointing to "/var/domotics". I'm using that link to load my app in the RAM area of the target. But the problem is: I only have about 7.6MB of free RAM available and if I don't strip my libstdc++ and libc libraries, I hit that limit. > tar gzipped version into the flash, then you can unpack it into RAM memory > the (/var/your_library) at boot time pushing the tar xzvf command into the > rc script and in this way you have lots of additional space. > (the library contains lots of ASCII ³symbols² so probably the compressor > will really reduce its size) Well, might be a possible solution to my problem. I didn't experiment yet with compressing/decompressing the libstdc++ during boot, so I can give this one a try too. However, if I untar libstdc++ in "RAM" space and on top of that I have my app (where, of course, libstdc++ is *not* statically linked in this case), will the "sum" of both not be the same as if I add libstdc++ statically to my application? After all, that library has to live somewhere. If not statically in my app, then dynamically in RAM. So, will I not end up having the same trouble? That's what I'm asking myself for the moment... Best rgds, --Geert
