| |
| |
On 8/16/20 9:18 AM Greg Ercolano wrote:
On 2020-08-15 11:36, Albrecht Schlosser wrote:
On 8/15/20 4:18 AM Greg Ercolano wrote:
On 2020-08-14 17:15, Albrecht Schlosser wrote:
But if things really need to be in <build>/bin for some reason,
then I'd next hope for:
<build>/bin/test/ <-- test executables
<build>/bin/examples/ <-- examples executables
... if it's important and more than one person ;-) wants it, I can
try it...
Sure, I'd like to see others weigh in on this.
FWIW: I created a proof of concept and found I could do it. Tested with
Linux, MinGW (MSYS2), and VS 2019. Since Xcode obviously uses the same
(multi-config build) structure as Visual Studio I assume this works as well.
Sounds great -- if you want me to test anything, just lemme know which branch
and I'll give it a spin.
Thanks, the new branch in my fork is 'feature-examples-subdir'.
You need to build the examples and after building with CMake you should
have the folders
- bin
- bin/test
- bin/examples
- data (+ subdirs)
Note that multi config builds like Visual Studio and Xcode have their
own subdirs per build type (Debug, Release, ...), e.g. bin/Debug,
bin/test/Debug, and bin/examples/Debug and the same for Release and
other build types.
Things we need to test on all platforms:
Run bin/test/demo and execute several test programs, particularly
- browser
- colbrowser
- editor
- help_dialog
- fluid
- ... and some more
I executed these tests on Windows with CMake/Visual Studio, CMake/MinGW
(MSYS2), and Linux (CMake + make and CMake + ninja).
The first 5 tests (incl. fluid) are executed with commandline args and
need to find their respective files in the 'data' folder. Other tests
just need to run and don't need any files.
Additional on macOS (which I can't do):
- build using CMake + make, run tests as above
- build using CMake + Xcode, run tests as above
Known issue on macOS: the wrapper scripts are always in the bin,
bin/test, and bin/examples folders and not in the "per build type"
subdirs Debug, Release, etc. where they belong. This will be fixed in a
later update (I think I know how to do it, but I need to implement and
test it).
TIA for testing.
--
You received this message because you are subscribed to the Google Groups "fltk.coredev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fltkcoredev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/fltkcoredev/d107fe54-108d-e776-c06a-02c245a560d0%40online.de.
[ Direct Link to Message ] | |
|
| |
