A recent job I landed through UpWork gave me the chance to set up a new application development workflow that I’ve been wanting to nail down which allows me to do all the development and testing of the windows applications on my Linux workstation.
Up till now I’ve been doing Windows development in a Windows10 VM utilizing Cygwin and wxWidgets. While very doable, I’m just not as efficient working in Windows. This comes from the majority of my last 20 years spent on Linux server and workstations.
So now I just have to:
- set up the Makefile to call the cygwin toolchain executables for g++, gcc, ld, and windres
- create a resource file for windres to set the APPINFO resources in the executable
- use Wine to do inital debugging and testing
- set up a shared folder with VMware to easily move executables and data to my WIN10 environment for further testing
Since this was a console application, one of the most tedious parts was to find just the right compile/link options to prevent Windows from opening a separate output window for the messages send to STDOUT.
In a nutshell the client had a large library of JPG photos dating back many years but were meticulously orgainized in a detailed folder structure. The goal of the application would be recursively descend a given directory structure, find all the JPG files, and add the TAGS to them based on parsing of the full directory path, including splitting tags where CamelCase, spaces, and numbers where found. All of the photos would then be loaded into Piwigo, which would use the embedded EXIF information to add the tags to the system when the files were imported.
Here is the Makefile I wound up using:
Let me know if you have any questions about how I set this up.
photo by Alex Andres from Pexels