-
Notifications
You must be signed in to change notification settings - Fork 132
after adding to environment variable PATH, build fails #1359
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
Comments
read a bit on other issues and tried setting the variable sloeber_path_extension to "c:\Git\bin" no change :/ |
On windows the paths is very sensitive and that is exactly why Sloeber uses FQN (fully qualified names) and reduces the path to the bare minimum. |
Hi jantje, I'm sorry but I didn't understand what I should exactly do to try your solution... meanwhile... |
should have said |
ok, now I understand. Thanks for the clarification. alas, it did not change things for the better :(
Apparently the git command now is found, executed correctly but still yields an error message... But still, make does not succeed either |
I'm not sure you are (only) hitting a path issue here Are you using the CDT prebuild functionality or are you modifying a platform.txt? |
I'm not sure of anything ;-) I use the "product", not the plugin ... and the trouble began...
|
I am only sure of 1 thing "everything is way more complicated than we think it is"
great to hear
That is true for everybody; though not all of us realize it. ;-)
smart move
I have no clue what git-hash is, how it is supposed to work or what it is supposed to do, how you tried to import it.
You mean ... you started to learn how much effort other people have done to get things to work 😉 and how fragile it is?
I can write a book about this. There are a couple of things to know in this area
|
Hi jantje, thank you for your kind words and - of course - your support ! I really do appreciate I am well aware how hard it can be to make things work. On the soft- and hardware side. And I also do know how painstakingly long it can be to track down and correct errors! And if I have learned one thing, then it is that the more complexity we bring into a system, the more fragile it becomes... I am very grateful for all the work that has been done to bring up really great products like sloeber, and even more to every person that besides creating these wonderful tools also are like always available to help when problems show up. Just for clarification as I think it has no impact on the current issue: when I write git-hash I am referring to the hash value that git gives every commit for identification purpose. I wanted to include that into my build process to be able to exactly identify the version of software that I produce. I read a bit on this subject and thought it a very smart way to keep track of different versions. I tired to install/upgrade to the nightly but I am not sure it worked... Installation details has a different look and sloeber is no longer listed under "installed software" but under "plugins", but still has 4.3.3 version number. Inspired by your remark of the presence of sh.exe in PATH and reading through issue #1198 I quickly checked for the presence of sh.exe using So, in short: Using the new make can resolve PATH issues in current 4.3.3 stable productAs far as I am concerned, this issue is resolved. But as I am not familiar with github and how things are managed I'd like to leave it to you to decide whether to close or not. Cheers, P.S.: if there is anything I can do to place a smile on your face, let me know! I am really thankful for your help :) |
alas, there still is a part that is not working now
For now I can work around this by manually renaming the make folder back and forth |
I do not understand your reasoning here. Building and committing are 2 different steps. IMHO creating a git-hash only is useful if you also committed your changes. Thanks for catching the clean issue. Seems make+sh does not support a del command but does support the rm command. |
Yes, you are right... And thanks again for the bits of extra-information you give! I learned a lot |
Where is this configuration folder to be found? |
In the root of the project with the same name as the configuration |
Oh, now I understand that this refers to the build configuration (Release as a default iirc) |
Can you try with the make in this zip and see if you can add the git folder to the path and build? |
I would, if I could find the .zip file... |
Strange I could have sworn I had added the link |
You did, over there in issue #1360 ;) |
I think that the workaround in #1360 is also applicable here: maybe it can be closed as well? |
indeed workaround |
HI,
I am trying to integrate automated git-hash inclusion as a pre-build step in Sloeber 4.3.3.202004230915 on Windows 10.
Therefore I had to add c:\git\bin to project->properties->C/C++ Build->Environment Variable PATH although git can be executed in a command prompt.
After that, the git command is executed but the build fails :/
This is the console output:
Only when I remove the added path, the build will be successful, but then the git command fails again as eclipse cannot find git executable.
I already tried adding path with ${PathDelimiter} instead of ';', or adding in front or at the end of the existing path, but no variant would lead to success.
Any ideas what I am doing wrong?
Cheers,
Bob
The text was updated successfully, but these errors were encountered: