I've tried that and compiled my git version of darktable now in the following way:
cd build cmake -DBINARY_PACKAGE_BUILD:BOOL=ON -DCMAKE_BUILD_TYPE=Release .. make sudo make install And that works, thanks! I compared now the two in different ways compiled variants that are working for me: The first with the editing of the CMakeList.txt, setting the flags -march=corei7-avx and -mtune=native and using the build.sh script and the second variant building with cmake and the option BINARY_PACKAGE_BUILD:BOOL=ON (which produced no -march flag but the flag -mtune=generic) Both variants of the compiled darktable are working good and at the same speed, so everything is ok. Why i've got the problem with the -march=native flag, maybe that my kernel is to old and does not detect my processor type exactly right. kernel 3.13.0-29-generic <--> Intel(R) Core(TM) i7-4765T Rico Am 20.06.2014 17:03, schrieb johannes hanika: > my cmake literacy is very limited, but you can abuse the > > BINARY_PACKAGE_BUILD:BOOL=OFF > > option (pass -D[..]=on to cmake when configuring). this is used for > redistributable binaries and will not use the -march=. flag. > > other than that i was under the impression that > > CFLAGS=<your flags> cmake > > would pick up the env var (note that most of dt is actually c and not c++). > not sure which one would be used then, the -march would still be added to > the flags by us. > > cheers, > jo > ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ darktable-devel mailing list darktable-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/darktable-devel
