Ballsy to show the MSFT stock in the screenshot…
To get the app into the repo, we’ll need a recipe, see the “Gentle introductions” at the haikuports wiki. Recipes for native applications are usually quite easy to write. See some of the apps under “haiku-apps” in the haikuports tree.
I used cross-develop on Mac ( lion / ssh connection to a bare metal machine). As I said, I just started developing on c++.
Do you have an error message for me?
Np Always glad to see people writing code for Haiku applications
The problem occurs with: add_executable(tests
[ 66%] Linking CXX executable tests
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: CMakeFiles/tests.dir/source/repository/RepositoryConfig.cpp.o: in function `RepositoryConfig::GetConfigFilePath()':
RepositoryConfig.cpp:(.text+0x9c): undefined reference to `BPath::BPath()'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: RepositoryConfig.cpp:(.text+0xad): undefined reference to `find_directory(directory_which, BPath*, bool, BVolume*)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: RepositoryConfig.cpp:(.text+0xbe): undefined reference to `BPath::Append(char const*, bool)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: RepositoryConfig.cpp:(.text+0xd2): undefined reference to `BPath::Append(char const*, bool)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: RepositoryConfig.cpp:(.text+0xda): undefined reference to `BPath::Path() const'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: RepositoryConfig.cpp:(.text+0x136): undefined reference to `BPath::~BPath()'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: CMakeFiles/tests.dir/source/repository/RepositoryConfig.cpp.o: in function `RepositoryConfig::GetConfigFilePath() [clone .cold]':
RepositoryConfig.cpp:(.text.unlikely+0x4): undefined reference to `BPath::~BPath()'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: CMakeFiles/tests.dir/tests/repository/TestRepository.cpp.o: in function `CATCH2_INTERNAL_TEST_0()':
TestRepository.cpp:(.text+0x2d0): undefined reference to `BString::BString(char const*)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: TestRepository.cpp:(.text+0x2db): undefined reference to `Repository::ReadFile(char const&, BString&)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: CMakeFiles/tests.dir/tests/gui/utils/TestQuoteFormatter.cpp.o: in function `CATCH2_INTERNAL_TEST_2()':
TestQuoteFormatter.cpp:(.text+0x6f): undefined reference to `QuoteFormatter::HumanReadableLargeNumber(float)'
/boot/system/develop/tools/bin/../lib/gcc/x86_64-unknown-haiku/11.2.0/../../../../x86_64-unknown-haiku/bin/ld: CMakeFiles/tests.dir/tests/gui/utils/TestQuoteFormatter.cpp.o: in function `CATCH2_INTERNAL_TEST_0()':
TestQuoteFormatter.cpp:(.text+0x42f): undefined reference to `QuoteFormatter::HumanReadableLargeNumber(float)'
collect2: error: ld returned 1 exit status
Every haiku package can be opened with the expander, don’t know how to protect the content here so that you can’t do this. But would be interesting to know.
There is a .receipe file that should build a package that I can publish on GitHub / HaikuDepot, but it won’t install. On “install stocks” HaikDeopt app tells me: “package… is not installable”
architecture should be either x86_gcc2 or x86_64. Using x86 means 32 bit but Haiku itself was built with gcc4+ as the primary compiler. This hasn’t been supported for a long time. There is some info on the package building page.
x86_gcc2 is almost always wrong. This is only for haiku internal packages build with gcc2. x86 is the secondary arch, yes. But it is the correct arch for almost all packages.
Added some suggestions upstream, was able to build/package/install on 64bit (app crashes though on launch (probably expected as it’s missing the API key as mentioned earlier). Hope it helps out a bit.