On Fri, 28 Apr 2006, Daniel Stenberg wrote:

> On Fri, 28 Apr 2006, Robert P. J. Day wrote:
>
> > locations: /a and /b on the build system for the sake of the
> > *build*, and /usr/local/whatever/libs on the *target* system for
> > runtime.
> >
> > what would the configure look like? thanks.
>
> If you want to play it the hard way,

actually, that's not the hard way -- there's no other way to do it if
you're cross-compiling. you can cross-compile openssl on your build
system, but you certainly can't do a "make install" since it's
meaningless to install that on your *build* system. in effect, you
have to leave the results of the openssl build where they are, and
somehow tell curl how to go find them. i see no other way to do it
cleanly.

> then your first approach to set LDFLAGS and CPPFLAGS to configure is
> the way to go.

i tried that as well, and it also didn't work -- the configure step
complained that it couldn't find an openssl installation. but
assuming that *is* the way to go, what would you supply as a
"--with-ssl" argument? remember, the libs and the headers are not in
the same location, so a single argument to --with-ssl is not going to
work.

rday
Received on 2006-04-29