Where is ldc.gccbuiltins_x86?

David Nadlinger via digitalmars-d-ldc digitalmars-d-ldc at puremagic.com
Thu Jan 21 16:23:30 PST 2016

On 22 Jan 2016, at 0:39, Dicebot via digitalmars-d-ldc wrote:
> I tried using something akin to -DCMAKE_INSTALL_PREFIX=/path/to/pkg 
> but it failed because of that mention bash-completion issue (tried to 
> write to /usr/share/bash-completion).

-DCMAKE_INSTALL_PREFIX=/path/to/pkg would prepare stuff to be installed 
to /path/to/pkg, which is not what you actually want for packaging. You 
wouldn't use --prefix=/path/to/pkg for an autotooled project either. For 
example, /path/to/pkg might end up being inserted into some config files 
that way. The bash-completion path issue is another manifestation of 
that – your system tells us that it wants the completion files in 
/usr/share/bash-completion, so we'll put them there by default.

DESTDIR is different. Its express purpose is to help with packaging (and 
similar scenarios like installing directly to a specially mounted 
chroot). For reference, see 
https://www.gnu.org/prep/standards/html_node/DESTDIR.html and 
https://wiki.archlinux.org/index.php/Arch_packaging_standards resp. 
https://wiki.archlinux.org/index.php/Creating_packages. You are doing an 
awesome job with LDC packaging – thank you! – so I don't doubt that 
the manual approach works for you. But maybe the usual automatic way 
will come in handy at some point. ;)

  — David

More information about the digitalmars-d-ldc mailing list