It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <gcc-help@xxxxxxxxxxx>
Subject: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
From: "Luiz Eduardo Gualti" <luiz.gualti@xxxxxxxxxxxx>
Date: Mon, 13 Mar 2006 12:35:06 -0300
Sender: gcc-help-owner@xxxxxxxxxxx

Hello !

I'm a new to GCC.

It's possible to use folder/file path for #define (like is possible to use
folder/file path into #indude statement) ? If yes, why ?

Regards

Luiz

Follow-Ups:
- Re: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
  - From: John Love-Jensen

Prev by Date: /usr/lib/amd64/crt1.o: file not recognized: File format not recognized
Next by Date: Re: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
Previous by thread: /usr/lib/amd64/crt1.o: file not recognized: File format not recognized
Next by thread: Re: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
Index(es):
- Date
- Thread

[Index of Archives] [Linux C Programming] [Linux Kernel] [eCos] [Fedora Development] [Fedora Announce] [Autoconf] [The DWARVES Debugging Tools] [Yosemite Campsites] [Yosemite News] [Linux GCC]

Powered by Linux