csnippets-bugs
[Top][All Lists]
Advanced

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

Re: [Csnippets-bugs] Errors when trying to compile


From: Allan Ference
Subject: Re: [Csnippets-bugs] Errors when trying to compile
Date: Sun, 13 Jan 2013 20:32:43 +0000

Hi Ron,

It seems that you're using an old revision, please do a git pull or re-clone the repository and try to re-compile. (I may have done a broken commit that led into that CMake error).

> The bool type is not defined in traditional C, only in newer standards or C++, so I add -Dbool=int to my compile options on GCC. But shouldn't there > be a better solution for users? I'm not sure what that should be - maybe something similar to this near the top of a header:
>
> #ifndef __cplusplus
> typedef int bool;
> #endif
>
> Or use stdbool.h? That should additionally have definitions for true and false, which are also used but are undefined and cause errors when I try to
> compile.

> No, there's a pre-compiled header in csnippets/, it includes the neccesary headers, it's called csnippets.h.  The CMake should generate the compiler directives for that.
Also, the example file client.c doesn't include stdlib.h header, which is needed. There are some more little problems like that. I've used compilers
> that automatically include files, and my compiler seems kind of strict about everything, but I'm just using normal settings for GCC over here. I'm
> concerned that other users will have difficulty trying to figure out these problems in order to successfully use the CSnippets code.
Ditto.

> The file socket.c tries to include internal/socket_compat.h, but this file was not in my computer (running a recent Debian, compiling CSnippets with
> GCC). I found a version of a file with the same name online, but I can't be sure it's the correct file or that it will work. Should the intended file perhaps > be included in CSnippets, or shouldn't users at least be told where they can find the file in a text file? Or am I missing something?
Yeah, that file was added in recent revision, you should update.

> I'm a noob to Savannah and collaborative programming, so I wasn't sure if I should report some of these issues as bugs, "fork the repository" and
> start making the changes that I feel are needed as time permits, or what.
"fork the repository" was intended if you're going to use github to develop, but that's not a must, it's just an option.  Another option is to generate patches via GIT and use git send-email to polish them to address@hidden.

Also, please provide your CMake and GCC versions.

Cheers,
Allan

reply via email to

[Prev in Thread] Current Thread [Next in Thread]