Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ALDORROOT #10

Closed
pbroadbery opened this issue Jul 17, 2013 · 3 comments
Closed

ALDORROOT #10

pbroadbery opened this issue Jul 17, 2013 · 3 comments

Comments

@pbroadbery
Copy link
Member

Setting ALDORROOT should not be required; applications ought not need a map to find their own backsides, er, files.

aldor currently does some of this, but it is easily confused.

@pippijn
Copy link
Collaborator

pippijn commented Jul 21, 2013

I have added a wrapper script that sets ALDORROOT as Waldek Hebisch' advised. This now works relatively well, but perhaps aldor should be told more about where its files are located. If people modify some of the dirs (e.g. libexecdir is different on Ubuntu than on Debian), it gets confused.

I'm somewhat reluctant to hard-code the paths into the binary, but putting more information into the wrapper script or a configuration file whose location is known (aldor.conf?) might be a solution.

@pbroadbery
Copy link
Member Author

The wapper script is good - there is some code in axlcomp.c which works off
argv[0] to set ALDORROOT, but it doesn't work in the case of aldor being
found via PATH. It probably should be killed offf.

Peter

@pippijn
Copy link
Collaborator

pippijn commented Jul 25, 2013

Commit 5ca3e2f allows external users to query configure-time variables from the wrapper script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants