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 ?

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

To: Luiz Eduardo Gualti <luiz.gualti@xxxxxxxxxxxx>, MSX to GCC <gcc-help@xxxxxxxxxxx>
Subject: 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 <eljay@xxxxxxxxx>
Date: Mon, 13 Mar 2006 10:57:53 -0600
In-reply-to: <MJEMJDDLGCKJBKHFBNNKEEMFDHAA.luiz.gualti@xxxxxxxxxxxx>
Sender: gcc-help-owner@xxxxxxxxxxx
User-agent: Microsoft-Entourage/11.2.1.051004

Hi Luiz,

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

I'm not sure what you are asking.

Is this what you are asking...

#define FOO "my/dir/bar.txt"

...?

Sincerely,
--Eljay

References:
- 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

Prev by Date: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
Next by Date: gcc -MM (anyway to exclude bracket headers)
Previous by thread: It's possible to use folder/file path for #define (like is possible to use folder/file path into #indude statement) ? If yes, why ?
Next by thread: gcc -MM (anyway to exclude bracket headers)
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