Another interesting thing to consider is modularity. Libreoffice allows you to
build individual modules of it but if problems are encountered a make clean is
run and a full rebuild is done. Also they integrate ccache to improve build
speeds as well.
Sent from my iPhone
> On 16 Jan 2017, at 09:55, marcel-hollerb...@t-online.de wrote:
>
> Hello,
>
>> On Mon, Jan 16, 2017 at 01:26:28PM +1030, Simon Lees wrote:
>>
>>
>>> On 01/16/2017 01:00 PM, Carsten Haitzler (The Rasterman) wrote:
>>> I'm going to bring this up as it's highly controversial... and not everyone
>>> is
>>> going to be happy, but doing NOTHING is worse.
>>>
>>>
>>> I propose that whatever we come up with should support at minimum the
>>> following
>>> build system "features":
>>>
>>> * configure --prefix=XXX
>>> * configure --bindir=XXX
>>> * configure --sysconfdir=XXX
>>> * configure --libdir=XXX
>>> * configure --includedir=XXX
>>> * configure --datadir=XXX
>>> * configure --localedir=XXX
>>> * configure --mandir=XXX
>>> * configure --docdir=XXX
>>> * at least all the relevant configure features we added for efl
>>> * make (from any dir/subdir)
>>> * make install
>>> * make uninstall
>>> * make DESTDIR=xxx
>>> * make dist
>>> * make distcheck
>>> * make check
>>> * cross-compiling (--host=XXX --build=XXX)
>>> * gettext support
>>>
>>
>> I'm feeling lazy but the output of openSUSE's cmake rpm macro is the
>> following and will answer some questions, cmake doesn't support make
>> dist out of the box, you could write a custom one or use something
>> called cpack (i've never used it), most projects just do a clean
>> checkout and tar it up and ship the tarball. "make check" can be done
>> with a custom command in cmake, cross compiling is also certainly supported.
>
> Just to clarify things a bit here:
>
> - cpack is quite easy you add a bit of configuration to your
> CMakeLists.txt and you have make package, this will then generate all
> the packages you have configured, those can be source-packages or
> directly a debian packages (just needs to be configured.
>
> - there is the test target, which is somehow what check is in efl. So
> if its okay to use a different target name, you dont even need a
> custom command.
>
>> -DCMAKE_INSTALL_PREFIX:PATH=/usr \
>> -DINCLUDE_INSTALL_DIR:PATH=/usr/include \
>> -DLIB_INSTALL_DIR:PATH=/usr/lib64 \
>> -DSYSCONF_INSTALL_DIR:PATH=/etc \
>> -DSHARE_INSTALL_PREFIX:PATH=/usr/share \
>> -DCMAKE_INSTALL_LIBDIR:PATH=/usr/lib64 \
>> -DCMAKE_BUILD_TYPE=RelWithDebInfo \
>> -DCMAKE_C_FLAGS="${CFLAGS:--O2 -g -m64 -fmessage-length=0
>> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
>> -fasynchronous-unwind-tables} -DNDEBUG" \
>> -DCMAKE_CXX_FLAGS="${CXXFLAGS:--O2 -g -m64 -fmessage-length=0
>> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
>> -fasynchronous-unwind-tables} -DNDEBUG" \
>> -DCMAKE_Fortran_FLAGS="${FFLAGS:--O2 -g -m64 -fmessage-length=0
>> -D_FORTIFY_SOURCE=2 -fstack-protector -funwind-tables
>> -fasynchronous-unwind-tables} -DNDEBUG" \
>> -DCMAKE_EXE_LINKER_FLAGS="-Wl,--as-needed -Wl,--no-undefined
>> -Wl,-z,now" \
>> -DCMAKE_MODULE_LINKER_FLAGS="-Wl,--as-needed -Wl,--no-undefined
>> -Wl,-z,now" \
>> -DCMAKE_SHARED_LINKER_FLAGS="-Wl,--as-needed -Wl,--no-undefined
>> -Wl,-z,now" \
>> %if "lib64" == "lib64"
>> -DLIB_SUFFIX=64 \
>> %endif
>> -DCMAKE_SKIP_RPATH:BOOL=ON \
>> -DCMAKE_VERBOSE_MAKEFILE:BOOL=ON \
>> -DBUILD_SHARED_LIBS:BOOL=ON \
>> -DBUILD_STATIC_LIBS:BOOL=OFF \
>> -DCMAKE_COLOR_MAKEFILE:BOOL=OFF \
>> -DCMAKE_INSTALL_DO_STRIP:BOOL=OFF \
>> -DCMAKE_MODULES_INSTALL_DIR=/usr/share/cmake/Modules
>>
>>
>> --
>>
>> Simon Lees (Simotek) http://simotek.net
>>
>> Emergency Update Team keybase.io/simotek
>> SUSE Linux Adelaide Australia, UTC+10:30
>> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
>>
>
>
>
>
>> ------------------------------------------------------------------------------
>> Developer Access Program for Intel Xeon Phi Processors
>> Access to Intel Xeon Phi processor-based developer platforms.
>> With one year of Intel Parallel Studio XE.
>> Training and support from Colfax.
>> Order your platform today. http://sdm.link/xeonphi
>
>> _______________________________________________
>> enlightenment-devel mailing list
>> enlightenment-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
>
>
> ------------------------------------------------------------------------------
> Developer Access Program for Intel Xeon Phi Processors
> Access to Intel Xeon Phi processor-based developer platforms.
> With one year of Intel Parallel Studio XE.
> Training and support from Colfax.
> Order your platform today. http://sdm.link/xeonphi
> _______________________________________________
> enlightenment-devel mailing list
> enlightenment-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
enlightenment-devel mailing list
enlightenment-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
