i2pd/Makefile.bsd

CXX = clang++
CXXFLAGS = -O2
## NOTE: NEEDED_CXXFLAGS is here so that custom CXXFLAGS can be specified at build time
## **without** overwriting the CXXFLAGS which we need in order to build.
## For example, when adding 'hardening flags' to the build
## (e.g. -fstack-protector-strong -Wformat -Werror=format-security), we do not want to remove
## -std=c++11. If you want to remove this variable please do so in a way that allows setting
## custom FLAGS to work at build-time.
NEEDED_CXXFLAGS = -std=c++11 -D_GLIBCXX_USE_NANOSLEEP=1
INCFLAGS = -I/usr/include/ -I/usr/local/include/
LDFLAGS = -Wl,-rpath,/usr/local/lib -L/usr/local/lib
LDLIBS = -lcrypto -lssl -lz -lboost_system -lboost_date_time -lboost_filesystem -lboost_program_options -lpthread
fixed FreeBSD build 2015-12-28 10:52:02 -05:00			`CXX = clang++`
Revert the 'clean-up' commits so that custom build-time flags can be set These commits removed the 'NEEDED' vars which were added so that CXX and LDFLAGS could be specified at build time. By doing away with these and using solely CXXFLAGS and LDFLAGS, special flags cannot be added. Indeed, specifying your own CXXFLAGS would cause the build to fail. We want the build flags to be APPENDED, not overwritten. 2014-12-17 20:24:36 +00:00			`CXXFLAGS = -O2`
add explanatory comments to Makefiles 2014-12-17 20:46:19 +00:00			`## NOTE: NEEDED_CXXFLAGS is here so that custom CXXFLAGS can be specified at build time`
			`## without overwriting the CXXFLAGS which we need in order to build.`
			`## For example, when adding 'hardening flags' to the build`
			`## (e.g. -fstack-protector-strong -Wformat -Werror=format-security), we do not want to remove`
			`## -std=c++11. If you want to remove this variable please do so in a way that allows setting`
			`## custom FLAGS to work at build-time.`
* Makefile.* : fix build with gcc 4.7.2 (#299) 2015-11-27 11:42:44 +00:00			`NEEDED_CXXFLAGS = -std=c++11 -D_GLIBCXX_USE_NANOSLEEP=1`
FreeBSD support 2014-08-11 09:51:53 -04:00			`INCFLAGS = -I/usr/include/ -I/usr/local/include/`
allow LDFLAGS to be set by user Move old LDFLAGS variable to LDLIBS. By doing ths, a user can set their own LDFLAGS without breaking the build. A case in which this can be useful is hardening with debian, e.g. $ dpkg-buildflags --get LDFLAGS -Wl,-z,relro 2014-10-30 22:47:19 +00:00			`LDFLAGS = -Wl,-rpath,/usr/local/lib -L/usr/local/lib`
* drop boost_regex from build deps 2016-05-27 00:00:00 +00:00			`LDLIBS = -lcrypto -lssl -lz -lboost_system -lboost_date_time -lboost_filesystem -lboost_program_options -lpthread`