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

Use binary output folder as the compiler's working directory #89

Merged
merged 1 commit into from
Mar 12, 2016

Conversation

osialr
Copy link
Contributor

@osialr osialr commented Mar 11, 2016

Reasoning
My root java project was getting filled with intermediate objects when using the MS compiler. This makes the compiler put it's object's in the architecture-specific directory. It may require updates to javacpp-presets to include only .so/.dll/.dynlib.

Open Question:
An alternative would be create a temp directory somewhere and then delete the files when the compile completes

This should prevent MSVC from dumping it's object files
in the project's root directory.
saudet added a commit that referenced this pull request Mar 12, 2016
 * Use the `outputDirectory` as the compiler's working directory
@saudet saudet merged commit 0c2b518 into bytedeco:master Mar 12, 2016
saudet added a commit to bytedeco/javacpp-presets that referenced this pull request Mar 12, 2016
…R files (pull bytedeco/javacpp#89)

 * Execute the `cppbuild.sh` scripts within the Maven build lifecycle, can be skipped with `-Djavacpp.cppbuild.skip` (pull #175)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants