Closed wlfbck closed 3 months ago
Hello, even though the include order may fix it, including the file cifXToolkit.h from your application should not be necessary. It's a toolkit internal file. It seems it's included by cifxlinux_internal.h (which is as well a driver internal) which is included by BigPBSlaveInstance.h. So please remove the include of cifxlinux_internal.h in BigPBSlaveInstance.h.
Oh, good catch. Removing those (completely unused) includes of cifxlinux_internal.h
solved the issue :)
Just out of curiosity, why does that define exist? Isn't that the same as the standard min?
To guarantee the most flexability the toolkit relies only on the minimal set of the standard C (ISO/IEC 9899) and there is no min/max function or macro. Some c libraries may provide fmin/fmax but they are used for floating point numbers.
Because of the min definition in cifxToolkit.h:
we are getting compilation problems because of this:
And several dozens more in various parts of the standard library.
I noticed that in our previous, very old, version of libcifx (1.0.0) this min define wasn't present yet.
Googling
macro "min" passed 3 arguments, but takes just 2
gives me a lot of results to not do that define. So is it necessary? Can it possibly be removed?(Sorry, usually we are not doing a lot of work in C++)