Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • F frama-c
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 173
    • Issues 173
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 1
    • Merge requests 1
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • pub
  • frama-c
  • Issues
  • #1142
Closed
Open
Issue created Jul 08, 2013 by mantis-gitlab-migration@mantis-gitlab-migration

Configure script's autolocation of local OcamlGraph breaks out of tree builds

ID0001454: This issue was created automatically from Mantis Issue 1454. Further discussion may take place here.


Id Project Category View Due Date Updated
ID0001454 Frama-C Kernel > configure public 2013-07-08 2014-03-14
Reporter sstewartgallus Assigned To virgile Resolution open
Priority normal Severity minor Reproducibility always
Platform - OS - OS Version -
Product Version Frama-C Fluorine-20130601 Target Version - Fixed in Version -

Description :

I prefer to build my software packages out of tree. My personal arrangement is to have one sources directory, and one builds directory. I would then run my packages configure script inside a subdirectory of the sources directory specifically for that package, and build from there.

It is great that a version of OcamlGraph is distributed with Frama-C but unfortunately the configure script can only find it if the current directory is the source directory, and this breaks out of tree builds.

The problematic line in configure.in appears to be:

  AC_CHECK_FILE($OCAMLGRAPH_LOCAL,OCAMLGRAPH_EXISTS=yes)

This line could probable be fixed in multiple ways. There's probably an autoconf macro for looking for a file in the source directory that's better than AC_CHECK_FILE, or one could define OCAMLGRAPH_LOCAL to use the invocation of ./configure to locate the directory it's located in (which would be something like ("$(cd $(dirname $0) && pwd)/ocamlgraph".)

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking