Forum Replies Created
-
AuthorPosts
-
b.timofteParticipant
Dont take it the wrong way but is a bad sign in a tool when you select something and it doesnt happen.
I tested a tool who was refusing to close the window options if an option was selected. That tool was very poorly tested and was scrapped.
I hope you guys know what are you doing and have some tests.
I have major problems with project wich has total nr of filenames(.c) longer than windows command length (8k chars on win7) I can imagine no one bothered to test it properly this situation and only a proj with a toy helloworld.cpp was tested and then you called it a day.
- This reply was modified 8 years, 5 months ago by b.timofte.
b.timofteParticipantb.timofteParticipantI wonder how you build this 9000+ files linux kernel -_-” using visualGDB … Really insipring
- This reply was modified 8 years, 5 months ago by b.timofte.
b.timofteParticipantHi
It didnt worked
The linker command looks wrong
C:/SysGCC/mingw32/bin/g++.exe -o Debug/WindowsProject1.exe -Wl,-gc-sections -Wl,–start-group @Debug/WindowsProject1.exe.in -Wl,–end-group
1>g++.exe : error : Debug/thisIsAveryLongFilenamY: No such file or directory
1> mingw32-make: *** [Debug/WindowsProject1.exe] Error 1
1> Makefile:137: recipe for target ‘Debug/WindowsProject1.exe’ failed
1> ————————————————————-
1> Command exited with code 2
1> Executable: cmd.exe
1> Arguments: /c “C:\SysGCC\mingw32\bin\mingw32-make.exe” -j8 CONFIG=Debug
1> Directory: C:\Users\timo\Desktop\Study\Embedded\STM32\VisualGDB\WindowsProject1\WindowsProject1
1>VisualGDB : error : Command-line action failed
1>EXEC : error : Build has failed. See the Output window for more details.
1>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.MakeFile.Targets(42,5): error MSB3073: The command “”C:\Program Files (x86)\Sysprogs\VisualGDB\VisualGDB.exe” /rebuild “C:\Users\timo\Desktop\Study\Embedded\STM32\VisualGDB\WindowsProject1\WindowsProject1\WindowsProject1.vcxproj” “/solution:C:\Users\timo\Desktop\Study\Embedded\STM32\VisualGDB\WindowsProject1\WindowsProject1.sln” “/config:Debug” “/platform:Win32″” exited with code 1.
========== Rebuild All: 0 succeeded, 1 failed, 0 skipped ==========b.timofteParticipantVisual Studio Import is slow.. taking forever … 20 minutes for 4000 .c files .
Visual GDB import recuresvily works in 10 seconds , but removal of Src folder again takes ages …
b.timofteParticipantI use Windows .exe project
Apply \Ok doesnt change anything. The only think that worked is to remove the stuff from .mak file
b.timofteParticipantThe VS GUI fucking blocks . I tested on Windows 10 and windows 7 with vs 2015
b.timofteParticipantIs this forum dead lol ?
I cant imagine i am the only one who compiles +1000 files.
Is it possible to give as input to mingw linker *.o instead of the full list of objects file ?
Maybe possible to tell the linker to make a list of object files in a file and give this file as input ?
Anyone ?!
b.timofteParticipantSo the tool calls the linker (g++.exe) with a HUUGE list of object files. I guess the command is too long
What solution shall i make ? Splitting the source code into smaller folder doesnt seems to work and its unreliable since the file number and filename length matters
b.timofteParticipantI think the command is too long (to make exe from .o)
Is there any FLAG where i can pass this limitation ?
- This reply was modified 8 years, 5 months ago by b.timofte.
b.timofteParticipantWhere should i add this option ? Your answer is not clear
b.timofteParticipantb.timofteParticipantWhat about affordable prices for hobbyst ? Do you expect me to pay 200$ for it ? Are you insane?
-
AuthorPosts