Forgive me, but I'm not familiar with editing a make file. I know they are used in Unix/Linux, but all the compiling I did there I didn't edit one. I am very much a newbie so any guidance would be greatly appreciate!
--- On Fri, 10/24/08, Ross Berteig <Ross@...> wrote:
> From: Ross Berteig <Ross@...>
> Subject: Re: [Mingw-users] newbie - can't get include and libs to work (Keith Marshall)
> To: mingw-users@...
> Date: Friday, October 24, 2008, 9:17 PM
> All in all, I'd call suggest pragmatic avoidance of
> spaces. They
> do improve the readability of long, descriptive file names
> in an
> all-GUI desktop, but they are not nearly as friendly to use
> the command prompt. At least CMD.EXE does file name
> and also adds the quotes on the assumption that the command
> be parsed following the minimal rules described by Roman
> in this thread.
> The various *nix flavors all allowed spaces in file names
> think that nearly any characters except slash and NUL were
> allowed in file names, and I know for certain that
> '*', '?' and
> most of the rest of the characters that were magic to the
> were also allowed), but no sane user of a shell prompt
> would dare
> do that because it always caused hassles. Shells that
> name completion were rare in those days too.
> These days on Windows, I let anything with a proper
> have its way with "C:\Program Files". I
> figure that if it came with
> an installer, then it knows what to expect. But I never
> install anything in that folder.
> For everything else, I keep folders named C:\Programs,
> C:\Programs\Bin inside it. Trivial useful command
> line tools get
> copied to C:\Programs\Bin, which is also in the
> system PATH.
> Larger packages without installers get their own folders in
> C:\Programs, and occasionally parts of them get added
> to PATH as
> well. MinGW is a good example of that category.
> I'm reasonably careful to keep my project development
> inside paths that lack spaces as well, and rarely put
> spaces in
> any name that is known to a tool chain.
> For things like Lua for Windows which got installed in
> Files but also provides include and lib folders for
> use, I'm simply careful in my Makefiles to get things
> right the first time. The system supplied PROGRAMFILES
> environment variable is handy for keeping things portable,
> long as you are careful with when and where the quotes
> get put on the name.
> All that said, I don't think it would have ever
> occurred to me to
> try to make a library available by editing the GCC config
> I would normally use the usual approach to getting -I and
> options into the GCC command line in the project's
> Otherwise, you've concealed the project's
> dependency on a
> third-party library and made it much more difficult for
> else to work with the source code.
> Ross Berteig
> Cheshire Engineering Corp.
> This SF.Net email is sponsored by the Moblin Your Move
> Developer's challenge
> Build the coolest Linux based applications with Moblin SDK
> & win great prizes
> Grand prize is a trip for two to an Open Source event
> anywhere in the world
> MinGW-users mailing list
> You may change your MinGW Account Options or unsubscribe