< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate] SSL Build Rules


Max:

Be careful with the handling of SSL_LOCATION (and similar variables) -- if we end up with system paths (like /usr/include or /usr/lib) in -I or -L switches, then the cross-compilation setup breaks in very bad ways that most people cannot easily troubleshoot.

As an aside, I note that the handling of the SSL build rules in the main Makefile is pretty badly messed up anyway, from a portability perspective (e.g., hardcoding for 32-bit linux configuration). My inclination would be to remove them -- we don't currently build any other external dependencies; I'm not sure why OpenSSL should be different. (In fact, I think this may be leftover cruft from before the DTLS work made it into the public OpenSSL project, in which case removal is absolutely the correct answer).

/a

svn@xxxxxxxxxxxxxxx wrote:
Project resiprocate
New Revision 8334
Committer maxb (Max Bowsher)
Date 2008-11-27 03:20:15 -0600 (Thu, 27 Nov 2008)

Log

 The directory 'contrib/openssl' does not exist, fix the Makefile rules to refer
 to '$(SSL_LOCATION)' instead.  (Partial fix, since $(SSL_LOCATION) is allowed
 to be blank - followup commit to come later.)
 
 

  

Modified:


_______________________________________________ resiprocate-commit mailing list resiprocate-commit@xxxxxxxxxxxxxxx https://list.resiprocate.org/mailman/listinfo/resiprocate-commit