On 17 Apr 2002 at 10:36, Jean le Roux wrote:
> On Tue, Apr 16, 2002 at 07:01:23PM -0700, Paul G. wrote:
> > A guess: libtool is looking for .so files and can't find them.
> > (libstdc++.so, libcrypto.so, etc.)
[On the target platform]
> Not sure I quite follow your train of thought, but here goes :)
> I bootstrap my project with
> ltmain.sh (GNU libtool) 1.4 (1.920 2001/04/24 23:26:18
> under Redhat7.1. The bootstrap includes a 'libtoolize' on my
> project. This means that the libltdl dir is added to the project, and
> that the libtool script is built on the target box, at configure time.
> I suppose this will count as a 'port from source'.
Looks like it. Thanks for clarifying. Please, bear with me as I make an attempt to get up to speed here.
When you say "project" in the above context, are you referring to the project on your box, or the project on
the target box? Not sure if it matters, but feel I am tracking something, but can't quite put my finger on it. At least not
I am thinking that you may need to actually reproduce (cross-compile, etc.) the necessary utilities under
MSYS (shell or otherwise) before you will be able to bootstrap the target box (assuming your target box is MSYS),
whatever that box may be.
Now, the title of this thread is "problem compiling dll's". From that standpoint, there are utiltities available
(either from Cygwin distro or Mingw-1.1 distro) that allow you to generate .dlls with relative ease. I am thinking that
you are already aware of those utilities.
The utilities, just to get it out of the way, if run separately are, gcc/g++ -c (to generate object code), and
dlltool [options] (to convert object code into .dll format). These specific utilities to generate .dlls are only available
within something which supports a Win32api environment since, afaik, they depend on the existence of the Win32api
in order to generate the requested .dlls. The MSYS development environment is capable of invoking those utilities.
Here is where things get kind of foggy for me. At bootstrap time, are you wanting to convert a particular set
of (existing) libs on your (RH) box to .dll libs for the target MSYS box or are you wanting to "enable" the ability to
link/generate/load .dlls on the MSYS target box?
Initially, it sounds like to me is that you are wanting to build .dlls On your target box and, for some reason or
another, are running into road-blocks when you attempt to build those .dlls. Is that correct?