Project

General

Profile

Support #1353

configure script help

Added by John Abbott over 4 years ago. Updated about 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
John Abbott
Category:
Documentation
Target version:
CoCoALib-0.99700
Start date:
27 Oct 2019
Due date:
% Done:

100%

Estimated time:
1.11 h
Spent time:
1.05 h

Description

Bruns recently asked (by email) if configuring CoCoALib with --no-boost will work OK.

I believe CoCoALib does not depend on BOOST at all; it is needed only for the CoCoA-5 interpreter.

Check this; and perhaps modify the help for configure so that it is clear that the BOOST options are relevant only for CoCoA-5.

Related issues

Related to CoCoALib - Design #933: Separate configure scripts for CoCoALib and CoCoA-5In Progress2016-09-30

Related to CoCoALib - Feature #1360: configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost)Closed2019-11-01

Related to CoCoALib - Design #1413: configure script: MODE option obsolete?Closed2020-02-11

History

#1 Updated by John Abbott over 4 years ago

  • Related to Design #933: Separate configure scripts for CoCoALib and CoCoA-5 added

#2 Updated by John Abbott over 4 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 20

I have just compiled CoCoALib with the option --no-boost, and everything worked fine (as I expected/hoped). Of course, CoCoA-5 did not build.

It may help to make a special section in the configure help message for options related just to CoCoA-5 (BOOST and readline).

#3 Updated by Anna Maria Bigatti over 4 years ago

  • % Done changed from 20 to 30

I think that --no-boost should be listed as a CoCoALib option, because it can compile without boost, instead of a CoCoA-5 option, because the latter cannot compile without boost, so that's non an option.

#4 Updated by John Abbott over 4 years ago

Ahhh. I see your point.

For CoCoALib the option --no-boost does nothing (since CoCoALib does not use BOOST, I believe).
This does make me feel that separate configure scripts for CoCoALib and CoCoA-5 might make better sense; though it will be (very) slightly more work for us when we want to compile a new version of CoCoA-5.

The current arrangement is potentially confusing for people who just want CoCoALib.

#5 Updated by Anna Maria Bigatti over 4 years ago

I have another suggestion: add the flag --only-lib that does --no-boost --no-readline and does not compile cocoa5.
Configuration should be faster, and also compilation (with no attempt to compile cocoa5)

#6 Updated by John Abbott over 4 years ago

  • Related to Feature #1360: configure script: add flags for "only cocoalib" or "both cocoalib and cocoa5" (for boost) added

#7 Updated by John Abbott over 4 years ago

  • Assignee set to John Abbott
  • % Done changed from 30 to 90
  • Estimated time set to 0.88 h

I think that the documentation for the configure script is clear enough now; so am moving this issue to feedback.
The issue (#1360) about the names for the options is separate.

#8 Updated by John Abbott about 4 years ago

  • Related to Design #1413: configure script: MODE option obsolete? added

#9 Updated by John Abbott about 4 years ago

  • Status changed from In Progress to Closed
  • % Done changed from 90 to 100
  • Estimated time changed from 0.88 h to 1.11 h

Anna finds current --help doc acceptable. Closing.

NOTE the help will almost certainly change when #1360 is implemented!

Also available in: Atom PDF