liberty-eiffel
[Top][All Lists]
Advanced

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

Re: [Liberty-eiffel] eiffel-iup on Windows


From: Germán Arias
Subject: Re: [Liberty-eiffel] eiffel-iup on Windows
Date: Tue, 08 Nov 2016 19:54:48 -0600

Mmmm... I think these new problems are caused by #include "iup.h" at my
C file in plugin directory. So, I don't have idea what is going wrong.

Germán

El mar, 08-11-2016 a las 19:30 -0600, Germán Arias escribió:
> I solve this problem adding some #include "my_file.h". I don't know
> why
> I don't have problem on GNU/Linux with this, but on Windows seems
> this
> is necessary. 
> 
> Now I have other problem. When I compile, the "se" tool add all the
> definitions of C function to one file called "iup.h". But all the
> float
> parameters are defined in this file as pointer. For example if I have
> a
> function like
> 
> my_function (float x, float y)
> 
> Then the function appears at "iup.h" like:
> 
> my_function (void* x, void* y)
> 
> And I get errors saying: 
> 
> "expected void* but argument passed is float"
> 
> I think this is an error on LibertyEiffel, but no idea how solve it.
> Any advice?
> 
> Germán
> 
> 
> El mar, 08-11-2016 a las 00:18 -0600, Germán Arias escribió:
> 
> 
> > Hi,
> > 
> > I'm testing eiffel-iup on Windows 10 32bits (with the new Windows
> > installer). But I have problems. I'm using gcc 4.8.1, because the
> > iup
> > binary packages are incompatible with gcc 6 (and I supposes also
> > with
> > gcc 5). Iup libraries work perfectly, I has been tested it with
> > examples in C. These compiles without problems and runs. But with
> > Liberty Eiffel I get this error:
> > 
> > bad reloc address in 0x0 section in '.data'
> > 
> > See attached screen shot. As far as I understand, this problem
> > appears
> > when you don't link the necessary libraries, or when you pass the
> > libraries in a wrong order to the linker. I get this error even if
> > I
> > link all the iup libraries, so I supposes the second (wrong order)
> > is
> > the problem. But can't figure how solve it. Any advice? Thanks
> > 
> > Germán
> 



reply via email to

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