[Pkg-phototools-devel] Bug#855359: Bug#855359: darktable: 2.2.1 binary very slow compared to self-compiled

[Roman Lebedev]

On Mon, Feb 20, 2017 at 10:08 AM,  <matthias at bodenbinder.de> wrote:
> Am 2017-02-20 0:36, schrieb David Bremner:
>>
>> Matthias Bodenbinder <matthias at bodenbinder.de> writes:
>>
>>> And by the way, this are the commands I use to compile DT:
>>>
>>> ./build.sh --disable-gnome-keyring --prefix /home/software/darktable
>>> --build-type Release
>>> cd build
>>> echo "darktable 2.2.1" > description-pak
>>> checkinstall --default --install=no --pkgname=darktable-mbo
>>> --pkgversion=$version --docdir=$INST/share/doc
>>>
>>> Matthias
>>
>>
>> The debian package does not use build.sh. I looks like build.sh does not
>> pass -DBINARY_PACKAGE_BUILD=1 to cmake.
>>
>> To test this, you could run something like
>>
>> mkdir -p dtbuild && cd dtbuild && cmake
>> -DCMAKE_INSTALL_PREFIX=/opt/darktable \
>>       -DCMAKE_BUILD_TYPE=Release  -DBINARY_PACKAGE_BUILD=1 ..
>>
>> then I guess your same checkinstall should work.
>>
>> d
>
>
> Hi,
>
> I do not understand your point. My checkinstall is working fine. It is just
> that my binaries are a lot faster than the debian testing binaries.
darktable custom-built binaries are optimized for whatever the host computer
is used during build.
debian packages do not have that luxury, they need to run on a wide variety
of hardware, so they are built with most generic optimizations possible

It is expected that self-compiled binaries may be faster than the .deb's

> Matthias
Roman.