Forum Replies Created
-
AuthorPosts
-
hfParticipant
ah…. stupid! i got it. I need to be on the blue command line. And exact this line can export to bat file.
Attachments:
You must be logged in to view attached files.hfParticipantHi,
here are the screenshots. Is this enough?
best regards
Attachments:
You must be logged in to view attached files.hfParticipantHi,
thanks the missing dialog is cleared.
But not fully solved 😉 If i right click, the context menu will show up “Dump command line to Batch File”
What should then happen? A Save Dialog for the Batch File? Or to which folder is the Batchfile written? I get no feedback when i click on the Menuitem.
Sorry for still not solved.
Best regards
Holger
hfParticipantHi Support,
i really followed this.
I will attach the screenshots. My Properties Windows looks different to yours in the ESP32 Project with cmake.
Best regards
Holger
Attachments:
You must be logged in to view attached files.hfParticipantHi,
we updated the support subscription. 😉
I have the problem, that i still not see the window, to activate the .bat generation.
Something missing?
Attachments:
You must be logged in to view attached files.hfParticipantUsing build with visualgdb /build
will result in a
“Your Makefile will nbot be auto-updated. Please go to VisualGDOProject Properties and click ‘repair command lines”
Currently is it really not possible to checkout by server and build is automatically?! also to generate the make files by cmake by itself? That would be a big pain.
Best regards
Holger
hfParticipantHi,
i have the same issues but i’m not able to set the local build.
I got this configurations window at the latest visual studio 2019 and visualgdb.
Where is now the option hidden? Has dies changes with the lastet cmake Changes? I would also build the project from a build server (in my case gitlab) with a local runner.
Best regards
Holger
- This reply was modified 3 years, 6 months ago by hf.
Attachments:
You must be logged in to view attached files.hfParticipanti checked everything.
allowed the firewall.
Deactivated Windows Defender.
ALso Installed Antivir to allow SessionServer.exe.
But nothing really helped. All changes were done with a restart of windows to have no artefacts in the running windows session. It’s really unclear, what blocks the Licencing. The revert to the Trial licence worked. But this is a temporaly workaround and no solution.
Hope to get it running soon.
hfParticipanti got a temporaly success!
I removed our floating licence and used the trial version.
Now it works.
But currently i have no clue, where the SessionServer gets blocked!
The Content filter of the firewall is deactivated and windows firewall is also open. I also see no blocking inside the firewall.
On which ports is the SessionServer communicating?
best regards holger
hfParticipantHi,
sorry this didn’t help. We use dedicated VM with no AV.
The Help-About screen shows our 4 floating licences.
Could it be the version of VS? I tried it with VS2015 and VS2017.
We had a similar problem with the ESP32 toolchain some time ago. On a different machine it worked.
hfParticipantHi,
thanks for the information. I appreciate your offer to integrate the ESPs to the Visual Studio.
I hope to hear soon about some updates 😉
hfParticipantHello,
thanks for the answer. This helped me a lot.
It seems, that the variables have no values, if the taskFunction is on the top level. If you call call a function (of a class) then the variables are shown correct.
This is a little issue, but is will not stop us to work on the project.
Thx
-
AuthorPosts