Just some quick reaction, I have to go now.
and HB_ETC_INSTALL or HB_CNF_INSTALL.
What is the difference between ETC and CNF?
If possible IMO we should not differentiate between
types of config files.
These are my propositions for our new envvar name.
Chose one of them. Personally I preffer th
On Tue, 22 Sep 2009, Szak�ts Viktor wrote:
Hi,
> Just some quick reaction, I have to go now.
>> and HB_ETC_INSTALL or HB_CNF_INSTALL.
> What is the difference between ETC and CNF?
> If possible IMO we should not differentiate between
> types of config files.
These are my propositions for our new
Hi Przemek,
Just some quick reaction, I have to go now.
and HB_ETC_INSTALL or HB_CNF_INSTALL.
What is the difference between ETC and CNF?
If possible IMO we should not differentiate between
types of config files.
/lib/
[//
On Sun, 20 Sep 2009, Szak�ts Viktor wrote:
[...]
Usually in system installation we have existing structure like:
/bin - with executable files, one of PATH dirs
we should not use any subdirectories here
/lib - with shared libraries, one of system library
On 2009 Sep 21, at 00:07, Przemyslaw Czerpak wrote:
On Sun, 20 Sep 2009, Szak�ts Viktor wrote:
Here if possible I'd like to see some syncing between *nix and
non-*nix. On non-*nix dlls are created in bin dir, while on *nix
they are created in lib dir. This isn't too good.
It will create seri
On Sun, 20 Sep 2009, Szak�ts Viktor wrote:
> Here if possible I'd like to see some syncing between *nix and
> non-*nix. On non-*nix dlls are created in bin dir, while on *nix
> they are created in lib dir. This isn't too good.
It will create series of problems. shared libraries have exectable
attr
1. what is system wide localization and what user customized and how
to detec them.
One clean / easy / universal solution is to consider it user customized
when it resides inside /home or /Users, and "system" location if
anywhere
outside that.
3. where to put static and shared libraries (
now with libharbour*.so installed in /boot/common/lib/harbour/,
things
don't find it.
Not now but from the beginning of adding default HAIKU localization
it was installed in:
HB_INSTALL_PREFIX=/boot/common
${HB_INSTALL_PREFIX}/bin/
${HB_INSTALL_PREFIX}/lib/harbour/
${HB_INSTALL_PREFIX
On Sun, 20 Sep 2009, Tamas TEVESZ wrote:
Hi,
> now with libharbour*.so installed in /boot/common/lib/harbour/, things
> don't find it.
Not now but from the beginning of adding default HAIKU localization
it was installed in:
HB_INSTALL_PREFIX=/boot/common
${HB_INSTALL_PREFIX}/bin/
${HB
needs more massaging apparently.
I have no opinion on these file placements, so pls just advise
what to do, or feel free to patch it the way it's best.
Brgds,
Viktor
On 2009 Sep 20, at 19:37, Tamas TEVESZ wrote:
hi,
now with libharbour*.so installed in /boot/common/lib/harbour/, things
don'
hi,
now with libharbour*.so installed in /boot/common/lib/harbour/, things
don't find it.
--
[-]
mkdir /nonexistent
___
Harbour mailing list
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour
11 matches
Mail list logo