Open uli42 opened 8 years ago
@Ionic : can you please have a look at my approach?
I'm not really a fan of static builds, for anything but critical system packages they don't make a lot of sense and break more easily than one might think - this is especially true for a full X.Org server copy...
Regarding your commit: I'm concerned that it looks like this would break shared builds. Not installing static libraries may be a way around this, but IIRC Debian ships static libraries as part of -dev packages, which are build requirements of nx-libs.
A static build will make it easier to have a portable version. Also you can easily support ancient archs that only offer ancient xlibs. It also starts quicker and makes ld_library_path obsolete.
It would be perfect if we could only link libnx_x11 statically but I failed doing so. Not sure if it can be done at all...
Vom Smartphone gesendet.
----- Ursprüngliche Nachricht ----- Von: "Mihai Moldovan" notifications@github.com Gesendet: 15.04.2017 15:41 An: "ArcticaProject/nx-libs" nx-libs@noreply.github.com Cc: "Ulrich Sibiller" uli42@gmx.de; "Assign" assign@noreply.github.com Betreff: Re: [ArcticaProject/nx-libs] nxagent static make target broken (#171)
I'm not really a fan of static builds, for anything but critical system packages they don't make a lot of sense and break more easily than one might think - this is especially true for a full X.Org server copy... Regarding your commit: I'm concerned that it looks like this would break shared builds. Not installing static libraries may be a way around this, but IIRC Debian ships static libraries as part of -dev packages, which are build requirements of nx-libs. — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub, or mute the thread.
Both targets do not work and fail with various problems.