Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Linux Tools Project » Autotools with other languages (Fortran and Python)(What to do to take advantage of autotools on other languages)
Autotools with other languages (Fortran and Python) [message #510795] Thu, 28 January 2010 11:41 Go to next message
N. Pinhao is currently offline N. Pinhao
Messages: 2
Registered: January 2010
Junior Member
Hi

I have been using autotools to work on a project involving C, Fortran and Python files and libraries.
Recently I have installed Eclipse, migrated my projects and I would like to keep using autotools.
However it seems that the Eclipse support of autotools is very much oriented only to C/C++.
Meanwhile I have tried to set or migrate my main (C/Fortran/Python) project to Eclipse/autotools and aside the fact that the selection of an autotools projects appears under C/C++, up to now it seems that my previous configure.ac and Makefile.am files are working well...
However I wonder what am I missing or what are the limitations of the present C/C++ oriented support of autotools in Eclipse?

If anybody else is interested in extending the autotools support in Eclipse to other languages, I may find some time to collaborate on this.
Re: Autotools with other languages (Fortran and Python) [message #510872 is a reply to message #510795] Thu, 28 January 2010 17:07 Go to previous message
Jeff Johnston is currently offline Jeff Johnston
Messages: 169
Registered: July 2009
Senior Member
An Autotools project is a form of CDT Makefile project. The Autotools plugin requires the CDT and uses various CDT extensions. For example, the actual running of the Makefile occurs in a CDT builder. Autotools adds a new builder which runs the configure step before the Make builder runs. The CDT doesn't restrict what's inside your Makefile so if you are actually building fortran or other files, it just works as long as the tools are around. The configure step is likewise ignorant of what you actually intend to use the configuration for.

The reason for the C/C++ focus is that extending the CDT to support Autotool'd projects was the initial goal of the plugin. There are many C and C++ autotool projects that could not build under the CDT without major command line interference. Our goal is and has been to improve the C/C++ development experience. Using the CDT allows us to reuse code (e.g. UI elements) so we don't end up reinventing the wheel. FWIW, there was once a proposal to try and extend the CDT to add other languages, but I haven't heard the idea mentioned in quite a while.

I can't say for sure all the issues you will run into as multi-language projects aren't supported/tested. Build errors in your non-C/C++ files won't get shown in your editor and your non-C/C++ files won't be indexed. You may not care about this. I would assume that the CDT indexer will do what it can with the existing C/C++ files and skip over the rest.

I would suggest you simply continue to try it out and report back what issues you run into.
Previous Topic:using libhover for 3rd party documentation
Next Topic:Autotools with other languages (Fortran and Python)
Goto Forum:
  


Current Time: Thu Apr 17 03:44:14 EDT 2014

Powered by FUDForum. Page generated in 0.27656 seconds