#25 closed enhancement (fixed)
Add more options Sherpa-config script
| Reported by: | Frank Siegert | Owned by: | Frank Siegert |
|---|---|---|---|
| Priority: | minor | Milestone: | |
| Component: | Unknown | Version: | 1.1.2 |
| Keywords: | Cc: | andy.buckley@durham.ac.uk |
Description
Request from Andy Buckley: Accept --libdir and --cppflags as arguments.
Attachments (0)
Change History (5)
comment:1 Changed 16 years ago by
| Cc: | andy.buckley@durham.ac.uk added |
|---|---|
| Resolution: | → fixed |
| Status: | new → closed |
comment:2 follow-up: 3 Changed 16 years ago by
I'm probably misunderstanding, too: so there is now only --libdir? Or also --ldflags and --incdir? I don't understand the argument for no --cppflags: I hope your sources don't use absolute #include paths to the install directory?!? --cppflags/--incdir are still useful for anyone who wants to compile against the Sherpa headers: I assume you mean there is now only one -I path required for Sherpa, rather than one for each module?
In case you aren't, I would recommend supplying "ready made" --cppflags, --ldflags arguments as well as the component --incdir/--libdir. Yes, using the components is trivial, but having --ldflags/--cppflags gives confidence that that's all you need to do to get your compile/link command right.
comment:3 Changed 16 years ago by
Replying to andy.buckley@durham.ac.uk:
I'm probably misunderstanding, too: so there is now only --libdir? Or also --ldflags and --incdir?
There is also --incdir and --ldflags (which already used to be there).
I don't understand the argument for no --cppflags: I hope your sources don't use absolute #include paths to the install directory?!? --cppflags/--incdir are still useful for anyone who wants to compile against the Sherpa headers: I assume you mean there is now only one -I path required for Sherpa, rather than one for each module?
Exactly. Of course no absolute #include paths. And as mentioned above, --incdir does exist.
In case you aren't, I would recommend supplying "ready made" --cppflags, --ldflags arguments as well as the component --incdir/--libdir. Yes, using the components is trivial, but having --ldflags/--cppflags gives confidence that that's all you need to do to get your compile/link command right.
Ok, good idea. Committed to trunk.
comment:4 Changed 13 years ago by
| Milestone: | → rel-old |
|---|
Added --libdir (on trunk). --cppflags is going to be unnecessary from version 1.2 on (because we are using full-path #include statements there), so not adding it anymore. Correct me, if I misunderstood your request.
Frank