Sam S wrote:
>> * Brian Dessent <blip> [2005-12-31 15:46:50 -0800]:
>>
>> Sam Steingold wrote:
>>
>>> Is it possible?
>>>
>>> simply put, it it possible to write something like this:
>>>
>>> int main () {
>>> size_t my_length;
>>> <some magic>
>>> printf("exe size=%lld\n",my_length);
>>> return 0;
>>> }
>>
>> All the methods mentioned so far are essentially hacks working
>> against the linker, doing stuff behind its back. Why not go with
>> the flow? Put your data in its own section, and write a linker
>> script to handle that section in the desired way. You can access
>> the address by referencing the linker script variables in your
>> source code. See section 3 of the ld manual, particularly 3.5.3.
>> This should work on any platform that uses ld.
>
> the problems with this is that the "data" that is being appended is
> not known at link time and appending it may not require C tools
> (ld/gcc &c).
Then your options seems to have shrunk to a "launcher" that basicly does
system("lisp.exe -M lispinit.mem")
Can you elaborate on _why_ the "single executable" is so important?
Having a monolithic application exe is hardly doable in most cases, AFAICS.
Unless you defer from using ANY external resources.
/H
--
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
