Chris,
the one-makefile build in 0.9.8 is broken.
If you like to go in this direction you should find target "files:" in
crypto/x509/Makefile and to replace Makefile.ssl with Makefile. Next add
new options(as example "Mingw32-unix") in util/mk1mf.pl:
=====================
--- util/mk1mf.pl.ORIG 2006-11-30 15:04:43.000000000 +0200
+++ util/mk1mf.pl 2007-07-11 23:21:59.000000000 +0300
@@ -35,6 +35,7 @@
"VC-CE", "Microsoft eMbedded Visual C++ 3.0 - Windows CE ONLY",
"VC-NT", "Microsoft Visual C++ [4-6] - Windows NT ONLY",
"Mingw32", "GNU C++ - Windows NT or 9x",
+ "Mingw32-unix", "GNU C++ - Unix",
"Mingw32-files", "Create files with DOS copy ...",
"BC-NT", "Borland C++ 4.5 - Windows NT",
"linux-elf","Linux elf",
@@ -141,6 +142,10 @@
{
require 'Mingw32.pl';
}
+elsif ($platform eq "Mingw32unix")
+ {
+ require 'Mingw32-unix.pl';
+ }
elsif ($platform eq "Mingw32-files")
{
require 'Mingw32f.pl';
=====================
Go in util/pl/ and create Mingw32-unix.pl based on Mingw32.pl with
correct directory separator, shell commands, assembler files, $ex_libs,
to check lib and link rules and etc.
After this instead of "make makefile.one" you should use "make files"
and "util/mk1mf.pl Mingw32-unix ... >makefile.one" and may be you will
succeed. If you like to build shared libraries above is not enough.
I found one-makefile build to complicated so that please look in tickets
mentioned in a post before.
Roumen
Andy Polyakov via RT wrote:
Hi,
According to our records, your request has been resolved. If you have any
further questions or concerns, please respond to this message.
No comments on the tracker entry.
Apparently I should have clicked on more buttons, when closing the
ticket, but there *is* comment in RT.
Please could you tell me how this is
resolved?
You've suggested approach that mimics .bat-based build, i.e. generating
big flat make-file, while we've chosen to discontinue it in favor of
Unix-like build procedure, i.e. having make traverse source tree for
Makefiles [see development branch]. In other words suggested approach is
not the approach we want/can afford to support. A.
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
______________________________________________________________________
OpenSSL Project http://www.openssl.org
Development Mailing List openssl-dev@openssl.org
Automated List Manager [EMAIL PROTECTED]
