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.

Sign up for GitHub

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

Jump to bottom

Update BUILDING.md #172

Merged
merged 1 commit into from
Mar 31, 2020
Merged

Update BUILDING.md #172

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions BUILDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,9 +74,13 @@ make -f Makefile-Standalone
# From top of clean tree
./bootstrap

mkdir out
cd out
../configure
mkdir build/<CONFIG>
cd build/<CONFIG>
../../configure <CONFIG ARGUMENTS>
```
Where `<CONFIG>` is something that describes what configuration (as described by `<CONFIG ARGUMENTS>`
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is it possible to make these steps part of a script that a user can run to set this up this way?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The Makefile-Standalone already embodies that of sorts. I'd be reluctant to be much more prescriptive than that since everyone has slightly different styles of working (in tree, out of tree, etc.).

Copy link
Contributor

@BroderickCarlin BroderickCarlin Mar 31, 2020 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It looks like you are missing a closing paren after <CONFIG ARGUMENTS>

of the tree you're planning to build, or simply `out` if you're not feeling creative.
```

# Build libraries
make
Expand Down