How to create a project from binary sources

[Abhijeet D Mhatre]

On Saturday 17 July 2004 6:39 am, Jose Sanchez wrote:
> Thanks for the help, that seems to work very well, however, when I tried
> to compile the project I got the following errors which I didn't get
> when I compiled using the command window:
> *compiling poll.c (gcc)
> *replace/replace.h:84: error: conflicting types for `scandir'
> */usr/include/dirent.h:242: error: previous declaration of `scandir'
> *replace/poll.c:57: warning: implicit declaration of function `alloca'
>
> ...

Hi
Do you mean that when you typed make at the command prompt it worked well but 
when you invokded make from the kdevelop using F2 key it gave the errors? 
Do your header files have the #ifndef ... #define ... #endif directives to 
avoid multiple declarations.

regards
Abhijeet D Mhatre

 


>
> compiling clientdata.cc (g++)
> *replace/replace.h:84: error: declaration of C function `int
> scandir(const char*, dirent***, int (*)(const dirent*), int (*)(const
> dirent**, const dirent**))' conflicts with
> */usr/include/dirent.h:242: error: previous declaration `int
> scandir(const char*, dirent***, int (*)(const dirent*), int (*)(const
> void*, const void*))' here
> *server/clientdata.cc:574: warning: unused parameter
> `player_device_devlist_t*req'
>
> compiling dev_blobfinder.c (gcc)
> */usr/local/include/rtk.h:32:21: gtk/gtk.h: No such file or directory
> */usr/local/include/rtk.h:143: error: parse error before "GtkWidget"
> */usr/local/include/rtk.h:145: error: parse error before '*' token
> */usr/local/include/rtk.h:148: error: parse error before '*' token
>
> Does someone has an idea how to correct these errors?
>
> thanks
>
> Jose
>
> Abhijeet D Mhatre wrote:
> >On Thursday 15 July 2004 8:15 am, Jose Sanchez wrote:
> >>Hi,
> >>
> >>I was wondering if someone has an idea or if this is possible.  We are
> >>working with a program called player which is used for networking
> >>robots.  For this program to run with our robots we had to write drivers
> >>and incorporate them in their sources.  However, since no one in our lab
> >>is familiar with automake and autoconf we wrote our files with Kdevelop
> >>and then we always have to compile from the terminal window by invoking
> >>make and them make install.  I was wondering if it is possible to create
> >>a project out of the sources so that we can include directly our files
> >>there and compile directly from kdevelop.
> >>
> >>Thanks a lot for any suggestions, comments and help.
> >>
> >>Jose
> >
> >Hi
> >  You can always try qmake.
> >I am a regular user of kdevelop and but dont quite understand the
> > complexity involved with autotools.
> >
> >So  when I have to deal with a project involving autotools I use qmake.
> >qmake -project invoked in the project directory will make a .pro file.
> >then running qmake will generate a makefile.
> >Once this is done you can use kdevelop and import the existing project
> >
> >This usually works well for most projects.
> >The beauty of this is you just have to mainitain your source tree. No need
> > to maintain the Makefile. However if you want link to new libraries etc
> > to your build you will have to maintain the .pro file which is very easy
> > to maintain.
> >
> >Let me know if this works
> >
> >regards
> >Abhijeet D Mhatre


-
to unsubscribe from this list send an email to kdevelop-request at kdevelop.org with the following body:
unsubscribe »your-email-address«