[M3devel] Sorry if FAQ, but there's no one...? :)

[Jay K]

build_standalone() should be the answer.

Are your Gtk+ libraries in Modula-3 or not?

If they are in Modula-3, then that makes sense.

 

 

As a quick hack, how about delete or move away the .a files that are being

used that you don't want used?

 

And, your config file doesn't say -static, right?

I've seen that in older ones.

 

Can you add build_standalone() to src/m3makefile

rm -rf LINUXLIBC

cm3 -commands

 

and look at it and/or show us?

 

This area is a bit wierd and gray imho, but will probably remain exactly asis.

  (I'm not saying we won't solve your problem. I think the current system already does.)

The full flexibility is not exposed..

That is, it isn't likely to let you pick and chose which lib is static and which is dynamic,

unless the library itself is build_standalone(), in which case always static.

 

 

 - Jay
 
> From: dragisha at m3w.org
> To: m3devel at elegosoft.com
> Date: Sun, 27 Sep 2009 13:34:23 +0200
> Subject: [M3devel] Sorry if FAQ, but there's no one...? :)
> 
> I would like to send a program binary to friend for review, with
> Modula-3 libraries linked statically so he does not need to install cm3.
> build_standalone() tries to link staticlaly Gtk+ libs I am using, and
> they have no .a files and I want them as .so's anyway.
> 
> LINUXLIBC6
> -- 
> Dragiša Durić <dragisha at m3w.org>
> 
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20090927/350d932c/attachment-0002.html>