On 26/06/15 15:58, Raoul Hecky wrote:
> If you read my first mail I explained that a "char nothing;" make the build
> work. But I don't know the internal implications of such a change. And
> cedric told me that it's not good :)
It doesn't matter because it's not allocated or accessed. I don't know
If you read my first mail I explained that a "char nothing;" make the build
work. But I don't know the internal implications of such a change. And
cedric told me that it's not good :)
--
Raoul Hecky
2015-06-26 16:52 GMT+02:00 Tom Hacohen :
> On 26/06/15 15:49, Raoul Hecky wrote:
> > Elementary.h
On 26/06/15 15:49, Raoul Hecky wrote:
> Elementary.h already has a extern "C" block and then includes elm_pref*
> headers
Shouldn't that be enough? Worst case, you could just add "char nothing;"
to the struct.
--
Tom.
Elementary.h already has a extern "C" block and then includes elm_pref*
headers
--
Raoul Hecky
2015-06-26 16:34 GMT+02:00 Tom Hacohen :
> On 26/06/15 15:30, Raoul Hecky wrote:
> > Hi all,
> >
> > With latest git, when building Calaos (which is a C++ project) with
> clang++
> > 3.6.1 I get a warn
On 26/06/15 15:30, Raoul Hecky wrote:
> Hi all,
>
> With latest git, when building Calaos (which is a C++ project) with clang++
> 3.6.1 I get a warning for every files that is build and that includes
> Elementary.h:
>
> In file included from /home/raoul/local/include/elementary-1/Elementary.h:158:
Hi all,
With latest git, when building Calaos (which is a C++ project) with clang++
3.6.1 I get a warning for every files that is build and that includes
Elementary.h:
In file included from /home/raoul/local/include/elementary-1/Elementary.h:158:
In file included from /home/raoul/local/include/el
