Skip to content

Trigger a environment update based on os or workspace change (version control) #682

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

Closed
thesoulkiller opened this issue Mar 16, 2017 · 2 comments
Assignees

Comments

@thesoulkiller
Copy link

Hello team,
Appreciated what you've developed, good work !
There is an issue about importing project from Git. The android project is created in Windows, and pushed to a git server. Then an import from Linux host caused such issue.

"A_Windows_PATH/make" all
Cannot run program "A_Windows_PATH/make": Unknown reason

Error: Program "A_Windows_PATH/make" not found in PATH
....

Then I tracked the problem is actually caused by a path variable:
JANTJE.MAKE_LOCATION - "A_Windows_PATH"

Then I made JANTJE.MAKE_LOCATION - Undefined, and it built successfully.
Cheers,
-Baris

@jantje
Copy link
Member

jantje commented Mar 16, 2017

This is nor really the same issue as this #34 but it is the same root cause and the workaround is the same.
From michael:

The issue is not fixed in itself but we've found a viable workaround to it:
.project is in .gitignore
a file .project.copy needs to be copied manually to .project the first time
selecting the project's properties and re-selecting the board/com port, results in the absolute paths being replaced with the correct ones.

So it's not perfect yet but we can live with it so well that I foregot about it.

@jantje
Copy link
Member

jantje commented Mar 19, 2017

Triggering a environment update when the "project changes from os" is not going to solve this issue as this will create a new .(c)project file each time. but it will enable to check in the .(c)project file in a smart way.
As the original issue is unsolvable I'll reassign this issue to detecting os change and acting upon it.

@jantje jantje changed the title V3- Make tool path error when Importing project with Git Trigger a environment update based on os change Mar 19, 2017
@jantje jantje changed the title Trigger a environment update based on os change Trigger a environment update based on os change (version control) Mar 19, 2017
@jantje jantje self-assigned this Mar 19, 2017
@jantje jantje added domain: configuration Configuring Sloeber does not work as docummented importance: improvement request OS: all labels Mar 19, 2017
@jantje jantje changed the title Trigger a environment update based on os change (version control) Trigger a environment update based on os or workspace change (version control) Apr 1, 2017
jantje pushed a commit that referenced this issue Apr 13, 2017
change

Also: Use board descriptor for upload instead of com port
@jantje jantje closed this as completed May 25, 2017
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