Project

General

Profile

Bug #149

Makefile dependencies

Added by John Abbott almost 12 years ago. Updated over 9 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Makefile
Target version:
Start date:
02 May 2012
Due date:
% Done:

0%

Estimated time:
Spent time:

Description

There are problems with dependencies for optional external libraries.

How to make these dependencies visible only when the user has configured to use them?

Perhaps "configure" can use symbolic links to choose between an empty dependency file (e.g. /dev/null perhaps?) or a true dependency file?


Related issues

Related to CoCoA - Bug #238: Cleaner CVS?Closed2012-09-26

Related to CoCoALib - Slug #701: Makefile; limit dependencies on external libsRejected2015-05-13

Related to CoCoA-5 - Feature #1007: (makefile) New "clean" target which does not clean documentationClosed2017-02-02

History

#1 Updated by Anna Maria Bigatti over 11 years ago

another possibility would be to check in (and distribute) Makefile_dependencies without external libraries (i.e. a "naked" CoCoALib)

... or remove all Makefile_dependencies and see if someone complains (i.e. if automatic generation does not work for some user)

#2 Updated by John Abbott about 10 years ago

JAA believes the correct approach is to have separate dependencies for internal dependencies and for external dependencies. The point is that internal dependencies should change only rarely, and can be made of relative paths (how??); external dependencies depend on where the external libraries are located (these could be paths relative to some Make variable??).

#3 Updated by Anna Maria Bigatti over 9 years ago

  • Target version set to CoCoALib-1.0

#4 Updated by John Abbott over 7 years ago

  • Related to Slug #701: Makefile; limit dependencies on external libs added

#5 Updated by John Abbott about 7 years ago

  • Related to Feature #1007: (makefile) New "clean" target which does not clean documentation added

Also available in: Atom PDF