Define constants/code per device (or device family) - like resources do support

thanks. I wonder why resources do support this out of the box and source code doesn't though...

evolution over time.  Resource overrides have been there for a long time and jungles came later.

It does work but eclipse marks the functions from those classes as  Undefined symbol one every build - the build seems to work though.

if you run the app with a build target it works without the error

Set a default config.  Something like this:

project.manifest = manifest.xml
srcBase=source
resBase=resources

# maps default
base.sourcePath=$(srcBase);source-nomaps
base.resourcePath=$(resBase)

# with maps
fenix5plus.sourcePath= $(srcBase);source-maps
fenix5plus.resourcePath = $(resBase);resources-maps

this works. Not really clean though - the compiler knows all valid devices so it should now that each device will have access to the referenced class and function

There is no target device when auto build is on in eclipse.  This will handle a "generic" device.  With the above, my app gets built without on-device map support for everything but the f5+

I'd like to ask you one memory and efficiency question related to this:

What should be preferred to use for constant strings that are NOT language specific?

E.g. if I want to know the devices name, I could define it like following and put different versions of this class inside the device specific source folders:

class DeviceInfo {
	static const DEVICE_NAME = "Fenix 6X";
}

I assume this is always the better way to have static non translateable strings, isn't it?

And one second question:

If I export my app, will I get build exceptions if one of the possible targets may not be able to build correctly because I may have forgotten to make some changes for one specific device?

not sure on q1, but on q2, ithe build of the iq fails if a compile fails.