openframeworks / openframeworks/openFrameworks
error: please edit OSCHostEndianness.h or define one of {OSC_HOST_LITTLE_ENDIAN, OSC_HOST_BIG_ENDIAN} to configure endianness
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 10.4k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 9
Description
1>f:\openframeworks\addons\ofxosc\libs\oscpack\src\osc\oschostendianness.h(122): fatal error C1189: #error: please edit OSCHostEndianness.h or define one of {OSC_HOST_LITTLE_ENDIAN, OSC_HOST_BIG_ENDIAN} to configure endianness (compiling source file ..\..\..\addons\ofxOsc\libs\oscpack\src\osc\OscOutboundPacketStream.cpp)
Just in case somebody is familiar with the error.
It happens sometimes (not always) when I generate my project with PG.
I don't know how to isolate the error bc I am using several addons...
Running patch-release main branch on Windows10 / VS2017.
Maybe I can edit oschostendianness.h manually, but I am not sure could be a problem, and wich endian mode to choose.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with addons/ofxosc/libs/oscpack/src/osc/oschostendianness.h and reproduce the generated project build on Windows 10 with VS2017. Determine why the endianness definition is sometimes missing when using PG and verify that the generated project compiles without the fatal error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100