Scott Hannahs

The bigEndian() check is a run time check. The #include <byteswap.h> is always included by the precompiler before the compile phase. It would have to be excluded by an #IFDEF or some other precompiler flag along with removing the actual call to bswap_32 also with an #IFDEF compiler directive.</byteswap.h>

Or if you want to be specific to Apple clang, it has the following relefant defines to avoid including bytesswap.h? #define __APPLE__ 1 #define __BYTE_ORDER__ __ORDER_LITTLE_ENDIAN__ #define __LITTLE_ENDIAN__ 1 #define __ORDER_BIG_ENDIAN__ 4321 #define __ORDER_LITTLE_ENDIAN__ 1234 #define __ORDER_PDP_ENDIAN__ 3412

Shouldn't endianess be determined by configure and byteswap.h only included if the system is big-endiean? Usualy configure is used to determine endianess at compile time.

Yes, both the Arm and X86_64 Apple systems are little endian. Can we just trigger not to call byteswap or include it ifdef Apple ?

I haven’t had time to look at it these days. I have had a series of crisis. I would like to get back to it though so thanks for the nudge. I am glad that you are interested in a MacOS version. I am not sure how to build a framework from a dylib but I will look into it. It should not be that hard…. ? Recompiling the tabview shim was as far as I got. But https://stackoverflow.com/questions/7562793/how-do-i-create-a-working-framework-with-dylib-files-in-xcode-4/7563064 may have some help. I use fink...

In running on MacOS it seems to not be a big issue. I have installed the HDF5.10 (using the package manger "Fink") and in running the gcc compile for linux with appropriate flags, I can build the dylib. % gcc -c -fPIC -I /opt/sw/opt/hdf5.v1.10/include/ -I /Applications/National\ Instruments/LabVIEW\ 2020\ 64-bit/cintools h5labview.c -o h5labview.o % gcc -dynamiclib -undefined suppress -flat_namespace h5labview.o -o h5labview.dylib Is it simple to link the call library functions to this new dylib?...

I will try to post the fixed versions via git. Am learning the vocabulary and I think it will be posted soon. There is an update upstream of a high priority bug patch and will include that.

Here are the dpg output and build output files