Closed vwheeler63 closed 1 month ago
This one might be required: https://github.com/lvgl/lv_port_pc_visual_studio/blob/master/Documents/HowToSynchronizeLvglRelatedSubmodules.md
In Eclipse I can just right click on the project and click "refresh" to get the new files. Isn't there a similarly simple way VS too?
This one might be required: https://github.com/lvgl/lv_port_pc_visual_studio/blob/master/Documents/HowToSynchronizeLvglRelatedSubmodules.md
In Eclipse I can just right click on the project and click "refresh" to get the new files. Isn't there a similarly simple way VS too?
In VS 2022, adding and removing files is is automatic by adding or removing them from the project directory (similar to PyCharm). In VS 2019, there is a fast way (hidden) way to add existing files (one at a time), explained in this stackoverflow article, and removing them is still manual, though easy (by right click).
If one could get VS 2022 past that error message (early in the description), then it would probably handle the missing/moved files automatically. For files that were moved, if one approaches it with VS 2019, it can be faster to edit the .vcxproj
file and change the paths. Especially if there are several of them.
Visual Studio C++ projects will note every file in the project configuration file. So, it need to use a tool to update.
Kenji Mouri
Visual Studio C++ projects will note every file in the project configuration file. So, it need to use a tool to update.
Ah.... Indeed my test with VS 2022 was with a VB.NET project.
I see that it compiles now as of the commits on 16-Sep-2024. Thank you, @MouriNaruto !
Hi, @MouriNaruto !
I notice that this project has the directory structure is (very usefully) preserved in the project, as opposed to Visual Studio's default of having all .c
files in one "folder" and all .h
files in another "folder" (which I really don't like for large projects). Do you have a utility program of some sort that modifies the .cproj
file to do that? If so, I would very much like to get it, since I am trying to maintain a (private) Visual Studio project that ONLY compiles the LVGL library as a compilation test before I submit code changes.
Would you mind sharing how you make lvgl/lv_port_pc_visual_studio
project so useful by preserving the directory structure?
Hi, @MouriNaruto !
I notice that this project has the directory structure is (very usefully) preserved in the project, as opposed to Visual Studio's default of having all
.c
files in one "folder" and all.h
files in another "folder" (which I really don't like for large projects). Do you have a utility program of some sort that modifies the.cproj
file to do that? If so, I would very much like to get it, since I am trying to maintain a (private) Visual Studio project that ONLY compiles the LVGL library as a compilation test before I submit code changes.Would you mind sharing how you make
lvgl/lv_port_pc_visual_studio
project so useful by preserving the directory structure?
The source code of the project definition generator is in this repository: https://github.com/lvgl/lv_port_pc_visual_studio/tree/master/LvglProjectFileUpdater
Kenji Mouri
The source code of the project definition generator is in this repository: https://github.com/lvgl/lv_port_pc_visual_studio/tree/master/LvglProjectFileUpdater
Excellent!! Thank you very much! 😄
I did a fresh clone of
lv_port_pc_visual_studio
and tried to open it in Visual Studio 2022, and I get this message in the middle of the display area of the file LvglWindowsSimulator.vcxproj:and this which it would not let me copy/paste so I got a screen shot:
Trying to build the project results in errors from missing files:
...and several others -- too many to try to list (estimate based on scanning the error list with my eyes, 1306 errors and warnings).
I tried changing the
lvgl
submodule's "current state" to:but none of them handled this problem. In fact, I cannot find any record of the
lv_glfw_mouse*.c
files existing in the recentlvgl/lvgl
repository. Are they pending in a PR that has not been merged yet?=========
Next, leaving the
lvgl
submodule on thev9.2.0
tag, I tried it again with Visual Studio 2019. I don't get the error opening the project as I do with VS 2022. But attempting to do a build (from scratch after aclean
) ends very quickly with the following errors:This project has been really important for my last project, and I would hate to think that others are missing out.
I kept a copy of the version of this project I was working with (in another place), so it is not currently broken, but I thought you should be aware of this if you were not already.
I see there is a branch for
release/v7
andrelease/v8.3
. If not already being done, may I suggest having a stable version inrelease/v9.0
and onward? That would be very helpful if this is not already in the plans.Kind regards, Vic