[viordash]

Hi
Sorry for the long absence.
I have checked the utilities you mentioned, mkfifo + netcat. They are in the system and work.
I would be very grateful if you extend the custom target interface so that I can fully run tests

[viordash]

Could you tell me how can I execute the new extra .mak file? I did not see this information in the specified link. Or do I need to remove the #VisualGDB: AutoSourceFiles line and write the commands manually in the existing makefiles?

[viordash]

<span class=”tlid-translation translation” lang=”en”><span class=”” title=””>Could you tell me how can I execute the new extra .mak file? I did not see this information in the specified link. </span></span>

<span class=”tlid-translation translation” lang=”en”><span class=”” title=””>Or do I need to remove the <span style=”text-decoration: underline;”>#VisualGDB: AutoSourceFiles</span> line and write the commands manually in the existing makefiles?</span></span>

[viordash]

I’ll figure out the syntax of the makefile, but I don’t know how to call the new makefile, assuming the auto-generated makefile cannot be modified.

Just need to be aware that in our production version, the build is run on a Linux machine using jenkins or gitlab-ci and therefore only makefiles are available, not any custom Visual Studio build steps.

[viordash]

Could you show by example how to include a new .mak file? Can’t seem to change the auto-generated Makefile and debug.mak?

[viordash]

For some reason we will have to stay on gnu make. And it would be nice if you add projects management

[viordash]

No success yet

And as I understand from the contents of the “xxxx-Debug.vgdbsettings”, now no need to restore the regex strings after updating the plugin?

Attachments:

You must be logged in to view attached files.

[viordash]

Thank you, now everything is correct

[viordash]

>> 1. attached “xxx-Debug.vgdbsettings”
>> 2 && 3. attached “2020-05-21_22-36-05.png”

Attachments:

You must be logged in to view attached files.

[viordash]

Thank you, warnings messages are fixed.

A minor comment, I noticed that the modification time for files and folders differs with time zone value (my tz is +3)

In attachment I put the screenshot “2020-05-21_22-05-03.png”

Attachments:

You must be logged in to view attached files.

[viordash]

So far, your decision has not helped. I noticed that the “Timestamp offset” setting only affects to files. But it has no effect on folders.
BTW, the time of folders on the build machine is constantly changing during compilation. But the modified time of the files, only if changed their contents.
Here are 2 messages, with different settings (10800 and -10800)
—-
Stderr line received ‘tar: Utils: time stamp 2020-05-20 18:58:57 is 10800.210223503 s in the future’
The target’s clock might be out-of-sync with this computer’s clock. Use the Tools->VisualGDB->SSH Host Manager->Host-wide Settings to configure the timestamp offset.
Current timestamp offset for viordash-virtual-machine is 10800 (generation=14).
make CONFIG=Debug
—-
Stderr line received ‘tar: Utils: time stamp 2020-05-20 19:00:06 is 10800.298549338 s in the future’
The target’s clock might be out-of-sync with this computer’s clock. Use the Tools->VisualGDB->SSH Host Manager->Host-wide Settings to configure the timestamp offset.
Current timestamp offset for viordash-virtual-machine is -10800 (generation=15).
make CONFIG=Debug

Utils is a folder, and its modification time on the build machine is Wed 20 May 2020 07:00:06 PM MSK

[viordash]

Hi.

I have same issue. “Stderr line received ‘tar: Utils: time stamp 2020-05-14 14:50:13 is 10798.260748773 s in the future'”

VisualGDB 5.5.5.3573.

Timestamp offset settings is not helped in my case. I don’t see any impact when changing the value.

Changing time in the build machine (Linux Mint) is helped, the warning messages are no longer displayed

[viordash]

Thanks. Your solution helped with my problem.

And the update seems good

[viordash]

I’ll do it later and let you know

[Author]

Posts