Skip to content

Device adapters whose names differ between Windows and non-Windows #825

@marktsuchida

Description

@marktsuchida

I knew about this but there are quite a few, it turns out.

Let's be careful not to add more in the future.
We should add some kind of test to prevent inconsistent naming.

But let's NOT go and rename them until we have both enforcement and plans (changing names does break existing .cfg files).

Currently, on Windows the filename of the .vcxproj becomes the adapter name. On non-Windows, the name is specified in the Makefile.am.

When device adapters are built by Meson in the future, it will be best for them to have a single name (although hacks could be used to preserve the split naming). We could offer compatibility by adding a way for device adapters to have aliases, or just decide to unify the names and break some config files. In most cases the Windows name seems to be better, but there are some exceptions.

DeviceAdapters:

Windows (vcxproj) Linux/macOS (Automake)
ASIwptr ASIWPTR
BaslerPylon BaslerCamera
CairnOptoSpinUCSF CairnOptospinUCSF
ChuoSeiki_MD5000 ChuoSeikiMD5000
ChuoSeiki_QT ChuoSeikiQT
NPointC400 nPoint
pE300 CoolLEDpE300
pE4000 CoolLEDpE4000
PI_GCS PIGCS
PI_GCS_2 PIGCS2
SmarActHCU-3D SmarActHCU3D
Thorlabs ThorLabs
ThrolabsSC10 ThorLabsSC10
TwainCamera TwainRGBCamera
XCite120PC_Exacte XCite120PCExacte
Yokogawa CSU22

SecretDeviceAdapters:

Windows (vcxproj) Linux/macOS (Automake)
ESIOImagingControllers ESImagingIOControllers
PolychromeV Polychrome5000

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions