Hub,

Sorry for all the confusion.  I'm trying to be as clear as I can.  Are you 
saying that:

  - You *have* successfully done a diving make, starting in the Abi tree, 
    which fires off a Makefile.abi build of libiconv 1.7?  

    AND

  - You believe that the same process should work on other platforms?  

If so, I'd love some tips from you on how to make that same process Just 
Work for me, too.  From a quick glance at the errors I get, it's not at all 
obvious how to get this working. 

I can think of at least 4 approaches here:

1.  Ensure that libiconv/Makefile.abi is totally XP, and pass any 
platform-specific info in as args.  (This is how WV and LIBICONV 1.0 were 
built.)

2.  Change the abi/src/config/requires stuff to get rid of Makefile.abi 
entirely, and invoke the configure-generated Makefile instead.  (This is how 
EXPAT and PSICONV are built.)

3.  Change the abi/src/config/requires stuff to invoke different, 
platform-specific makefiles within libiconv (for Win32, this would be the 
.msvc variants), and then copy the results over into our tree so they can be 
linked. 

4.  Expect people to build libiconv manually.  

bottom line
-----------
#4 is unacceptable, and #3 is undesirable, so I'd like help with #1 or #2, 
unless someone can think of something better.  

Thanks,
Paul

Reply via email to