Well, the problem is that I am compiling on WinNT using msvc (I know, I
know... they make me.)  Since it's NT, I can't do any symbolic linking...
Plus, I work on a product that uses a directory structure and build options
that I don't get to change very easily (the build group can't handle too
many changes at once).  Any "vendor" (openSSL in this case) incs have to be
in a directory that is a peer of the code I am writing.  Making it #include
<openssl/xyz.h> forces me to either change them all back to the way they
used to be (i.e. witout the "openssl/", go back to SSLeay0.9.0.b, or spend
6-8 weeks of writing supporting documentation to petition the powers that be
to change "the way it is" so that I can get the changes made to use OpenSSL
(try justifying this to somebody who doesn't know anything about it).
-E

-----Original Message-----
From: Richard Levitte - VMS Whacker [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, June 28, 2000 4:05 AM
To: [EMAIL PROTECTED]; [EMAIL PROTECTED]
Subject: Re: Advice from a friend


From: "Moyle, Ed (PCA)" <[EMAIL PROTECTED]>

EMoyle> May I humbly request that in future updates of the library,
EMoyle> the following line (and all others like them) be changed back
EMoyle> from:

Oh, you may ask...  However, the move to require 'openssl/' was to
avoid conflicts with other headers.  And honestly, what's so bad with
havign that kind of identification?  Or would you want all X headers
to step down from 'X11/' as well?

EMoyle> I think the latter is friendlier, but this is just IMHO.  I
EMoyle> had to make a bunch of changes to my usage to get it to
EMoyle> compile cleanly.

Hmm, noone really stops you from adding -Ipath/include/openssl to your
compiling command, although it's not recommended...

-- 
Richard Levitte   \ Spannvägen 38, II \ [EMAIL PROTECTED]
Chairman@Stacken   \ S-168 35  BROMMA  \ T: +46-8-26 52 47
Redakteur@Stacken   \      SWEDEN       \ or +46-709-50 36 10
Procurator Odiosus Ex Infernis                -- [EMAIL PROTECTED]
Member of the OpenSSL development team: http://www.openssl.org/
Software Engineer, Celo Communications: http://www.celocom.com/

Unsolicited commercial email is subject to an archival fee of $400.
See <http://www.stacken.kth.se/~levitte/mail/> for more info.


______________________________________________________________________
OpenSSL Project                                 http://www.openssl.org
User Support Mailing List                    [EMAIL PROTECTED]
Automated List Manager                           [EMAIL PROTECTED]

Reply via email to