Hi,
>
> You should not do it like this. Never every copy files to /usr/lib or so.
> If the user decides to install openal later, it will conflict with your
> install.
Michael van Canneyt is correct. Under Linux, that is a bad idea and
can cause all sorts of problems. As he pointed out, there are
> All this is not "installing in Linux" (which is the OS) but rather something
> like "installing in a desktop Distribution"
>
> Does this work correctly with any distribution ?
>
> -Michael
>
Hm, I don't know, works on ubuntu :) . This is script from some HOWTO article
--
___
2012/8/7 :
> If you want to create a script that installs it anyway, make sure it
> installs in to /opt/yourprogram/
> with directories
> bin
> lib
>
> Libraries go into lib. Then create a startup shell script in
> /opt/yourprogram/bin that adds /opt/yourprogram/lib
> to the
> LD_LIBRARY_PATH envi
Am 07.08.2012 11:09, schrieb Michael Schnell:
On 08/07/2012 10:20 AM, Krzysztof wrote:
But what with linux? I have installation script which:
- Copy executable to /usr/bin
- Copy icons to /usr/share/icons
- Add application to desktop menu bo copying .destkop file to
/usr/share/applications
A
On 08/07/2012 10:20 AM, Krzysztof wrote:
But what with linux? I have installation script which:
- Copy executable to /usr/bin
- Copy icons to /usr/share/icons
- Add application to desktop menu bo copying .destkop file to
/usr/share/applications
All this is not "installing in Linux" (which is
On Tue, 7 Aug 2012, Krzysztof wrote:
Hi,
I have application which use openal.dll / openal.so library.
On windows this is easy and clear. I just put all files into InnoSetup
installer and my application find DLL in own directory.
But what with linux? I have installation script which:
- Copy
Hi,
I have application which use openal.dll / openal.so library.
On windows this is easy and clear. I just put all files into InnoSetup
installer and my application find DLL in own directory.
But what with linux? I have installation script which:
- Copy executable to /usr/bin
- Copy icons to /u
