On Fri, Oct 01, 1999 at 10:01:24AM -0400, Jonathan Lupa wrote:
> I agree that makefiles are the way to go, but I often like to
> prototype unfamilliar language features before I use them in
> production code. I guess I'm still screwed if I need to specify
> unweildly include paths or such since a
On Fri, Oct 01, 1999 at 03:04:56AM +0100, Mark Brown wrote:
> The command "g++" (also known as "c++") exists to do exactly this job -
Thanks! This is what I was looking for. For whatever reason,
I was still laboring under the misconception that egcs and g++ were
not one and the same.
I agree tha
On Wed, Sep 29, 1999 at 05:29:00PM -0400, Jonathan Lupa wrote:
> Is there a way to set an environment variable with the args I want for the
> egcc line?
The traditional approach is to use a Makefile. However...
> For example, I like STL, and am always typing `egcc -Wall -lstdc++ foo.cpp`.
> It
> "Jonathan" == Jonathan Lupa <[EMAIL PROTECTED]> writes:
Jonathan> This is more of a egcc question than a Debian question, but
Jonathan> after looking through the man page, I didn't find an answer
Jonathan> so here we go...
When dealing with GNU software, info is usually a better source than
This is more of a egcc question than a Debian question, but after looking
through the man page, I didn't find an answer so here we go...
Is there a way to set an environment variable with the args I want for the
egcc line?
For example, I like STL, and am always typing `egcc -Wall -lstdc++ foo.cpp
5 matches
Mail list logo
