Re: [Filecaddy-developers] Large Makefile changes...

[David J. K. <dke...@ko...>]

I'm totally ok with ditching Palm-DefaultVars.make and Palm-CustomVars.make
but I'm not ok with hard coding "m68k-palmos-gcc" (or any other specific
executable names) in the makefile and relying on the PATH. Using the PATH
environment variable (instead of specifying the full path to the executable
in the command) significantly slows down builds on some systems.

Keep the makefile using things like CC, PILRC, PALMRC, and OBJRES just as it
does now and then document at the top that the user has to define those
environment variables to match where he/she has the tools installed before
running the makefile. Move any non-tool env vars that Palm-DefaultVars and
Palm-CustomVars set up (and that we still need) into the top of the
makefile. Then it's trivial to set up a little "fc-dev.setup" script that
sets all the correct environment variables whenever you want to work on
FileCaddy (and if you want to "export CC=m68k-palmos-gcc" and then rely on
PATH to find it you can).

As for the brain fart that Sony calls the Hi-res API (and here I thought
they couldn't do worse than they did with VFS), make sure anything you add
for that (including #includes) is totally conditional. No one should be
forced to have the Clie SDK in order to build FileCaddy. We should probably
also consider two releases once that's in place so that non-Sony users don't
have to deal with the bloat that the hi-res API causes.

-- 
    - Dave Kessler
      President - Kopsis, Inc.
      http://kopsisengineering.com


On Fri, Aug 09, 2002 at 05:13:21AM -0700, Matthew Bevan wrote:
> This time I'm asking before blundering ahead ;)
> 
> Since FileCaddy no longer uses any Handspring-related APIs (there was no
> practical reason for me to inflict them upon my system in the first
> place, if you think about it ;) is there a way to avoid using the
> Plam-DefaultVars.make and Palm-CustomVars.make files?
> 
> I.e. just have m68k-palmos-gcc IN THE PATH, instead of having a makefile
> that defines the location.  After installing the new Prc-tools package,
> I encountered countless errors where I had to shift files around, or
> tweak them to get them working with FileCaddy again.  Not to mention
> Sony SDK...
> 
> That's another thing - Sony High-Resolution support.  Seems easy enough
> to add (and has been requested for VFSBrowser in the past) so I've added
> it to the to-do list.
> 
> -- 
> Matthew (Darkstorm) Bevan       mb...@ma...
> Margin Software, NECTI.		http://www.marginsoftware.com
> 	Re-inventing the wheel, every time.
> 
>  - After your lover has gone you will still have PEANUT BUTTER!
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Filecaddy-developers mailing list
> Fil...@li...
> https://lists.sourceforge.net/lists/listinfo/filecaddy-developers