Bug 248951 - CDT 4.0 doesn't recognize binaries create by Autotools projects
CDT 4.0 doesn't recognize binaries create by Autotools projects
Product: Fedora
Classification: Fedora
Component: eclipse-cdt (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Jeff Johnston
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2007-07-19 15:54 EDT by Jeff Johnston
Modified: 2008-02-12 15:49 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-02-12 15:49:22 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jeff Johnston 2007-07-19 15:54:02 EDT
In the latest Autotools build that works with CDT 4.0.0, when binaries are
created by an Autotools project, they are not recognized as such by the CDT and
they do not appear in a Binaries folder under the project nor do they have a
default run action associated with them (one has to set up a run dialog entry).

The problem is traced to the fact that Autotools projects use a separate build
directory that is set up as part of the configure tool.  The CDT does not
recognize changes to the build directory made for the project and is defaulting
to the configuration name ("Build (GNU)") when looking for binaries.  This has
been confirmed by manually creating the folder and copying in an executable binary.
Comment 1 Jeff Johnston 2008-02-12 15:49:22 EST
Problem fixed.

Note You need to log in before you can comment on or make changes to this bug.