Re: classpath problems with 0.9.5

From: Ulrich Köster (ulric..ssense.com)
Date: Fri Jan 10 2003 - 11:06:43 EST

  • Next message: Ian McDougall: "RE: [ANN] WOLips release 0.9.6"

    I`m fine with it. I may suggest that the classes goes in woproject.

    Am Freitag, 10.01.03 um 16:35 Uhr schrieb Markus Nolte:

    > okay, forget NEXT_HOME_ROOT, what about reading wo.root, wo.localroot &
    > wo.systemroot from wobuild.properties once and set them as NEXT_ROOT,
    > NEXT_SYSTEM_ROOT, NEXT_LOCAL_ROOT as classpath variable in eclipse?
    >
    > ----- Original Message -----
    >> From: "Ulrich Köster" <ulric..ssense.com>
    > To: "Markus Nolte" <m.nolt..eusta.de>
    > Cc: "Christian Edward Gruber" <cgrube..srafil.net>;
    > <woproject-de..bjectstyle.org>
    > Sent: Friday, January 10, 2003 4:08 PM
    > Subject: Re: classpath problems with 0.9.5
    >
    >
    >> Hi,
    >>
    >> it`s a good idea to handle this woproject/wolips internally . This
    >> also
    >> means that some stuff in wolips should move into woproject to keep it
    >> under one interface.
    >>
    >> If we replace ${user.home}/Library with NEXT_HOME_ROOT we get a
    >> circular reference. NEXT_ROOT is stored in the file
    >> WOBuild.properties. To find the file under NEXT_HOME_ROOT we need to
    >> resolve NEXT_ROOT..........
    >>
    >> But we need a place to store the NEXT_ROOT. The lookup in the
    >> environment takes a long time and pop ups a window under windows.(May
    >> be that is the reason why it's called windows.) :-)
    >>
    >> Ulrich
    >> Am Freitag, 10.01.03 um 13:52 Uhr schrieb Markus Nolte:
    >>
    >>> This is a good idea. We can use NEXT_HOME_ROOT instead of
    >>> ${user.home}/Library for things like wobuild.properties (e.g.
    >>> NEXT_HOME_ROOT
    >>> =${user.home}/.WOLips).
    >>>
    >>> Uli, what do you think about this?
    >>>
    >>>> Here's an approach that might solve the
    >>>> problem of /System and /Local on OSX vs. c:/Apple and C:/Apple/Local
    >>>> on
    >>>> NT. I propose we use the GNUstep approach.
    >>>> On OSX
    >>>> NEXT_ROOT = /
    >>>> NEXT_SYSTEM_ROOT = ${NEXT_ROOT}/System
    >>>> NEXT_LOCAL_ROOT = ${NEXT_ROOT}/Local
    >>>> NEXT_HOME_ROOT = ${HOME}/.OpenStep (or whatever)
    >>>> [I'm used to Nextstep and Mach, not OSX, so HOME_ROOT might be wrong
    >>>> in
    >>>> this example]
    >>>>
    >>>> On Windows
    >>>> NEXT_ROOT = C:/Apple
    >>>> NEXT_SYSTEM_ROOT = ${NEXT_ROOT}
    >>>> NEXT_LOCAL_ROOT = ${NEXT_ROOT}/Local
    >>>> NEXT_HOME_ROOT = ${USERPROFILE}/.OpenStep
    >>>>
    >>>> The above means that NEXT_SYSTEM_ROOT and NEXT_LOCAL_ROOT could be
    >>>> the
    >>>> basis of the patterns, obviating the issue around /System/Local
    >>>>
    >>>> Regards,
    >>>> Christian.
    >>>
    >>>
    >>
    >>
    >
    >



    This archive was generated by hypermail 2.0.0 : Fri Jan 10 2003 - 11:07:05 EST