PurpleI2P
/
i2pd
mirror of https://github.com/PurpleI2P/i2pd.git
1
0
Fork 0
Code Issues Releases Activity
I2P: End-to-End encrypted and anonymous Internet https://i2pd.website/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1938 Commits
11 Branches
76 Tags
28 MiB
Tree: c939dec26a
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c939dec26a'
${ noResults }
i2pd/Makefile.bsd

13 lines
722 B
Raw Normal View History Unescape

use standard make variables
10 years ago
CXX = g++
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.
10 years ago
CXXFLAGS = -O2
add explanatory comments to Makefiles
10 years ago
## 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.
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.
10 years ago
NEEDED_CXXFLAGS = -std=c++11
FreeBSD support
11 years ago
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
10 years ago
LDFLAGS = -Wl,-rpath,/usr/local/lib -L/usr/local/lib
LDLIBS = -lcryptopp -lboost_system -lboost_date_time -lboost_filesystem -lboost_regex -lboost_program_options -lpthread