Alright, so please humor me and reiterate 1,2,3 the procedure for each OS.
1) Mac - debug externally and production in *any* internal folder (although
generally "frameworks").
2) Linux - ?
3) Windows - ?
....it might not exist, but I'm looking for the most cross-platform compatible
method(s)
and a continuous thank you for your input.
Michael
------- Original message -------
From: Chris Little <cslittle at mac dot com>
Sent: 31.7.'07, 13:24
> The paths are a little strange. The paths are interpreted.
> "@executable_path" resolves to the real executable inside the package. The
> "../" after that moves up a folder. So you can see that the debug version of
> the constant moves up out of the package while the release version points to
> a file in the Frameworks folder inside the package.
>
> Chris
>
> on 7/31/07 1:14 PM, lists at mgreg dot com at lists at mgreg dot com wrote:
>
> > I guess, before saying "arbitrary", I should ask what "@executable_path"
> > resolves to. Per a previous post it was used for both debug and production
> > constants.
> > So, if, in fact, it resolves to the same place, then the need for a
> > different
> > location does seem arbitrary.
> >
> > So, how does linux handle the same issue?
> >
> > Michael
> > ------- Original message -------
> > From: Charles Yeomans <yeomans at desuetude dot com>
> > Sent: 31.7.'07, 12:48
> >
> >> It's not arbitrary. As I explained earlier, when you build a debug
> >> app, the REALbasic IDE does not provide a way to add the library to
> >> the debug application bundle. So you need to put the library
> >> somewhere else, and declarations in debug apps must specify that
> >> location.
> >>
> >> I'd guess that RS doesn't make it "intuitive" because this is a Mac
> >> OS problem only, and only a problem for "advanced" developers. I
> >> believe that RS gives lower priority to single-platform problems, and
> >> especially single-platform problems that only affect developers who
> >> know enough to find a way to work around the problem.
> >>
> >> Charles Yeomans
> >>
> >> On Jul 31, 2007, at 12:20 PM, Michael Williams wrote:
> >>
> >>> I'll check the book out. As I said, despite repeated explanations,
> >>> my confusion is still regarding the fact that there is a need to
> >>> differentiate between debug and production builds. Using a constant
> >>> just makes sense, but the need for the value to be different
> >>> depending on which it is seems a bit arbitrary. I guess I'm curious
> >>> as to why RB doesn't make it "intuitive"; a sort of "add-plugins-or-
> >>> dylibs-here" type of reference if nothing else.
> >>>
> >>> Anyway, I'll get to reading. Thanks for the help thus far.
> >>>
> >>> Regards,
> >>> Michael
> >>> On Jul 31, 2007, at 12:01 PM, Charles Yeomans wrote:
> >>>
> >>>> Use a constant to refer to the library. Set it for different values
> >>>> for debugBuild and not debugBuild. I think this sort of thing is
> >>>> discussed in my online declares book.
> >>>>
> >>>> Charles Yeomans
> >>>>
> >>>
> >> _______________________________________________
> >> Unsubscribe or switch delivery mode:
> >> <http://www.realsoftware.com/support/listmanager/>
> >>
> >> Search the archives:
> >> <http://support.realsoftware.com/listarchives/lists.html>
> >
> > _______________________________________________
> > Unsubscribe or switch delivery mode:
> > <http://www.realsoftware.com/support/listmanager/>
> >
> > Search the archives:
> > <http://support.realsoftware.com/listarchives/lists.html>
>
>
> _______________________________________________
> Unsubscribe or switch delivery mode:
> <http://www.realsoftware.com/support/listmanager/>
>
> Search the archives:
> <http://support.realsoftware.com/listarchives/lists.html>
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives:
<http://support.realsoftware.com/listarchives/lists.html>
|