You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we have a bunch of #define flags fed by the makefile as g++ -D... arguments during the build. But after we build a library file (libsnark.a or libsnark.so), the information on choice of flags is lost. Later, if a user compiling against the libsnark library happens to use different flags, all bets are off. This is especially bad because some of our code is in .c files (so affeceted by the flags when compiling libsnark), and other is in .tcc files (so affected by the flags when compiling the user's app).
Let's save the flags into a libsnark_config.h file and #include it from all pertinent places in libsnark, instead of passing g++ -D arguments. Then, make install can then install it with the rest of the headers.
The text was updated successfully, but these errors were encountered:
tromer
changed the title
Save #define flags into an .h file
Save #define flags into libsnark-config.h
Oct 23, 2015
Currently we have a bunch of #define flags fed by the makefile as
g++ -D...
arguments during the build. But after we build a library file (libsnark.a
orlibsnark.so
), the information on choice of flags is lost. Later, if a user compiling against the libsnark library happens to use different flags, all bets are off. This is especially bad because some of our code is in.c
files (so affeceted by the flags when compiling libsnark), and other is in.tcc
files (so affected by the flags when compiling the user's app).Let's save the flags into a
libsnark_config.h
file and#include
it from all pertinent places in libsnark, instead of passingg++ -D
arguments. Then,make install
can then install it with the rest of the headers.The text was updated successfully, but these errors were encountered: