Lorenzo Bettini writes:
> On 05/03/2011 01:11 PM, Lorenzo Bettini wrote:
>> On 05/02/2011 02:59 PM, Bastien ROUCARIES wrote:
>>> On Mon, May 2, 2011 at 12:02 PM, Lorenzo Bettini
>>> wrote:
On 04/25/2011 06:36 PM, Bruno Haible wrote:
>
> Lorenzo Bettini wrote:
>>
>> on the ma
Lorenzo Bettini wrote:
> actually I see that in the build directory (in the subdirectory where
> gnulib headers are generated) there's no stdint.h and stdbool.h, so I
> should be OK, right?
Then you are likely OK.
If you want to be sure, grep the header files that your library installs
for 'boo
On 05/03/2011 11:57 PM, Bruno Haible wrote:
Lorenzo Bettini asked:
Would it be correct to put config.h only say in file1.cpp (and use the
‘-I’ option that refers to the Gnulib library directory for that file
only), and not in file2.cpp and file3.cpp (where I don't use -I to refer
to gnulib libra
On 05/03/2011 01:11 PM, Lorenzo Bettini wrote:
On 05/02/2011 02:59 PM, Bastien ROUCARIES wrote:
On Mon, May 2, 2011 at 12:02 PM, Lorenzo Bettini
wrote:
On 04/25/2011 06:36 PM, Bruno Haible wrote:
Lorenzo Bettini wrote:
on the manual I read
"These Gnulib substitute header files rely on bei
Lorenzo Bettini asked:
> >> Would it be correct to put config.h only say in file1.cpp (and use the
> >> ‘-I’ option that refers to the Gnulib library directory for that file
> >> only), and not in file2.cpp and file3.cpp (where I don't use -I to refer
> >> to gnulib library directory), and then lin
On 05/02/2011 02:59 PM, Bastien ROUCARIES wrote:
On Mon, May 2, 2011 at 12:02 PM, Lorenzo Bettini
wrote:
On 04/25/2011 06:36 PM, Bruno Haible wrote:
Lorenzo Bettini wrote:
on the manual I read
"These Gnulib substitute header files rely onbeing already
included. Furthermoremust be
On Mon, May 2, 2011 at 12:02 PM, Lorenzo Bettini
wrote:
> On 04/25/2011 06:36 PM, Bruno Haible wrote:
>>
>> Lorenzo Bettini wrote:
>>>
>>> on the manual I read
>>>
>>> "These Gnulib substitute header files rely on being already
>>> included. Furthermore must be the first include in every
>>> com
On 04/25/2011 06:36 PM, Bruno Haible wrote:
Lorenzo Bettini wrote:
on the manual I read
"These Gnulib substitute header files rely on being already
included. Furthermore must be the first include in every
compilation unit. This means that to all your source files and likely
also to all your t
On 04/25/11 00:44, Lorenzo Bettini wrote:
> So the compilation problem goes away if I put config.h in all source files,
> but is that really necessary?
I'm afraid so. The alternative is pretty messy, and nobody
has had time to explore it. I wouldn't want to be the first
explorer myself.
Lorenzo Bettini wrote:
> on the manual I read
>
> "These Gnulib substitute header files rely on being already
> included. Furthermore must be the first include in every
> compilation unit. This means that to all your source files and likely
> also to all your tests source files you need to ad
Hi
I've been using gnulib for some years now in my GNU packages, but I was
wondering whether I'm using correctly, since some people reported some
compilation errors on some architectures...
I'm using getopt module, and on that architecture the user gets this
compilation error
g++ -DHAVE_CO
Hi
I've been using gnulib for some years now in my GNU packages, but I was
wondering whether I'm using correctly, since some people reported some
compilation errors on some architectures...
I'm using getopt module, and on that architecture the user gets this
compilation error
g++ -DHAVE_CO
Hi
I've been using gnulib for some years now in my GNU packages, but I was
wondering whether I'm using correctly, since some people reported some
compilation errors on some architectures...
I'm using getopt module, and on that architecture the user gets this
compilation error
g++ -DHAVE_CO
13 matches
Mail list logo
