Unfortunately the Cygwin environment can't be statically linked both by
design and by license.
The license requires that you distribute the entire thing or not at all.
And there's no way in the tools that they provide to statically link in the
.dll file.
One of these days, once I become independe
On Nov 19, 2007, at 10:36 AM, Curt, WE7U wrote:
A better recommendation would be to use the VMWare image inside
VMWare Player, assuming that the end-user machines are adequate to
run VMWare. That way you can run Linux inside VMWare and use either
the Xastir-LSB version or a custom compiled ver
On Sun, 18 Nov 2007, Craig Anderson wrote:
> Anyone know if I can compile 'static' under Cygwin? How
> much of the Cygwin environment can get linked in? How
> "stand-alone" will that binary be? No Cygwin install?
I don't know that I would recommend going for a Cygwin static
install. If you we
Thanks Brad & Jeremy,
Yes, I'm going against the trend of the last few decades
of computer science research here, but with some reasons.
If I'm going to ask a lot of RACES folks who are not Linux
wizards to install Xastir on their laptops, all those screwy
libraries to maintain will be a d
On Mon, 19 Nov 2007, Brad Douglas wrote:
> Basically, you need to compile all dependents to create static libraries
> (*.a). Not terribly difficult, but not necessarily trivial, either.
See the Xastir/scripts directory for the scripts I use to build
LSB-compatible statically-linked versions of m
On Sun, 18 Nov 2007, Craig Anderson wrote:
> Is it even
> possible to compile Xastir statically and
> end up with one giant binary that is not
> dependent on having all these libraries
> installed everywhere?
For the most part, yes. It can be done, and is being done: Called
Xastir-LSB, for "Lin
Hey Craig,
Yes, it's certainly possible to have a static binary, but I don't really
see the point unless the libraries used are only used for Xastir and
nothing else.
Basically, you need to compile all dependents to create static libraries
(*.a). Not terribly difficult, but not necessarily trivi
Hi all,
I must be get'n old and out of touch.
But I remember the days when we used
to compile things static and not have all
these dynamic libraries that get lost and
out of date and incompatible. Is it even
possible to compile Xastir statically and
end up with one giant binary that is no
