Skip to content

Commit

Permalink
ci: Rename macro to avoid conflict during CI unity builds (#4092)
Browse files Browse the repository at this point in the history
Unity builds (which we do for CI to speed it up) combine source files,
sometimes in ways that are a bit non-deterministic, and can run into
violations of the ODR that were not a problem when separate definitions
of the same thing (a macro in this case) were in different compilation
units but are in the same one as a unity build.

In this case, a private OIIO_DISPATCH_TYPES macro in printinfo.cpp
conflicted with a different macro of the same name in
imagebufalgo_util.h.

Signed-off-by: Larry Gritz <[email protected]>
  • Loading branch information
lgritz authored Dec 24, 2023
1 parent d887b78 commit e6c85b5
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions src/oiiotool/printinfo.cpp
Original file line number Diff line number Diff line change
Expand Up @@ -149,7 +149,7 @@ dump_flat_data(std::ostream& out, ImageInput* input,


// Macro to call a type-specialzed version func<type>(R,...)
#define OIIO_DISPATCH_TYPES(ret, name, func, type, R, ...) \
#define PRINTINFO_DISPATCH_TYPES(ret, name, func, type, R, ...) \
switch (type.basetype) { \
case TypeDesc::FLOAT: ret = func<float>(R, __VA_ARGS__); break; \
case TypeDesc::UINT8: ret = func<unsigned char>(R, __VA_ARGS__); break; \
Expand Down Expand Up @@ -211,8 +211,8 @@ dump_data(std::ostream& out, ImageInput* input,

} else {
OIIO_UNUSED_OK bool ok = true;
OIIO_DISPATCH_TYPES(ok, "dump_flat_data", dump_flat_data, spec.format,
out, input, opt, subimage);
PRINTINFO_DISPATCH_TYPES(ok, "dump_flat_data", dump_flat_data,
spec.format, out, input, opt, subimage);
}
}

Expand Down

0 comments on commit e6c85b5

Please sign in to comment.