RE: True Static Linking

RE: True Static Linking

[Robert Collins]

> -----Original Message-----
> From: Westley Weimer [mailto:weimer@EECS.Berkeley.EDU] 
> Sent: Wednesday, April 17, 2002 1:50 PM

> I am willing to have "hello.exe" be fairly large, but 
> shipping all of cygwin1.dll (700K) is not allowed. If this 
> were linux I would pull all of the .o files out of cygwin1.a 
> (or whatever) and link against a subset of them manually. I 
> have no idea how to do this under cygwin.

You can't under linux you would have to ship the vmlinuz file as well -
which is what cygwin1.dll is closest to in this environment.
 

Rob

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

True Static Linking

[David Starks-Browning]

On Tuesday 16 Apr 02, Westley Weimer writes:
> I am using gcc under cygwin and I would like to ship hello.exe to a friend
> who does not have cygwin1.dll on his computer.
> ...
> (1) Is there a "-static" switch that statically links in cygwin1.dll?

Read the FAQ entry "Can I build a Cygwin program that does not require
cygwin1.dll at runtime?"

> (2) If not, how else can I solve this problem?

Have them install Cygwin.  If they only want the "cygwin" package from
the Base category, they can de-select all the other packages that
would otherwise be installed by default.

Regards,
David


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: True Static Linking

[Sam Edge]

> (1) Is there a "-static" switch that statically links in cygwin1.dll?
> (2) If not, how else can I solve this problem?

I'm fairly new to Cygwin but from what I've picked up there is no static version of the cygwin library available either binary or source. This is a deliberate policy to try to ensure that all running Cygwin processes have the same version loaded and are all using the same shared memory and other kernel objects that are required to simulate the UNIX/POSIX API on top of the Win32 one.

If your program really needs things like fork() or native Berkley sockets you could get the source for Cygwin and patch it to generate your own static version. I've no idea how difficult this might be and maintaining it with newer versions would be a headache. (It may be that a DLL is required by the Win32 architecture for some of the features.)

I doubt whether a simple stand-alone executable needs this.

The first thing to do is to try the "-mno-cygwin" switch on gcc as well as making everything else statically linked. You might get away with this providing you're not relying on Cygwin-specific API calls or C++ standard template libraries. (Make sure you've used SETUP.EXE to install the mingw-runtime and w32api packages first.)

If that's not enough, you can go to http://www.colomsat.net.co/freehost/ngiraldo/cppcygwin.html to add the additional C++ STL. This has instructions for ensuring that you get what you need in a painless manner and can create native Win32 applications with the Cygwin GCC tool chain and all the other nice Cygwin 

(The other approach is to avoid using Cygwin as the development environment and to download the MinGW Win32-native GCC tols and libraries from http://www.mingw.org/, although this shouldn't be needed if you've configued everything correctly in Cygwin.)

MinGW relies on the Micrsoft MSVCRTx.DLL run-time libraries but these are pretty much universal. There is in fact no such thing as completely static linkage under Windows since you always end up dynamically linking to SYSTEM32, USER32, GDI32 and/or other "universal" Win32 system DLLs. The VC runtime are pretty much in this category.

-- 
Sam Edge


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

True Static Linking

[Westley Weimer]

I am using gcc under cygwin and I would like to ship hello.exe to a friend
who does not have cygwin1.dll on his computer.

	$ gcc -v
	Reading specs from /usr/lib/gcc-lib/i686-pc-cygwin/2.95.3-5/specs
	gcc version 2.95.3-5 (cygwin special)
	$ gcc hello.c -o hello.exe -static

Unfortunately, this does not work because cygwin1.dll is not present on the
target computer. You can simulate the problem as follows:

	$ PATH= ./hello.exe
	[ Windows Error Box:
	    The dynamic link library cygwin1.dll cannot be found in the
	    path C:\WINNT ... ]

I am willing to have "hello.exe" be fairly large, but shipping all of
cygwin1.dll (700K) is not allowed. If this were linux I would pull all of
the .o files out of cygwin1.a (or whatever) and link against a subset of
them manually. I have no idea how to do this under cygwin.

(1) Is there a "-static" switch that statically links in cygwin1.dll?
(2) If not, how else can I solve this problem?

Thanks!

	- Wes


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/