nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: Configuration with cygwin nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210: nico@210:
nico@210: nico@210: next nico@210: nico@210: up nico@210: nico@210: previous nico@210: nico@210: contents nico@210:
nico@210: Next: Compilation with Visual Studio nico@210: Up: Visual Studio C++ nico@210: Previous: Requirements nico@210:   Contents nico@210:
nico@210:
nico@210: nico@210: nico@210:

nico@210: Configuration with cygwin nico@210:

nico@210: Follow instructions given at nico@210: a422Cygwinconfigurationandcompilationoutline4.2.2)Cygwin nico@210: configuration and compilation, but do neither call make nor do tests, nico@210: just do configuration steps. This will create headers files accordingly nico@210: to your configuration parameters, and the desired CAN hardware. nico@210: nico@210:

nico@210:

nico@210:
nico@210: epimerde nico@211: 2007-06-06 nico@210:
nico@210: nico@210: