To things weren't even really compatible to begin with.
So, if you have access to an old raspberry pi, that would be the easiest way to build it for your target (armhf) architecture.
Another option is to use qemu virtualisation.
So I'm afraid that I lack a lot of critical information about what that improvised computer can do.
:/
I can however try to ask a coworker in a few minutes.
Okay, but then that's maybe not a question for this forum. If you are going to cross-compile for an embedded device, that's quite a specialised discipline... I can try to compile oat++ on my lime2 this afternoon (which is 32 bit arm), but that one runs a full debian distro.
What do you get after running
file ../ext/oatpp-1.3.0/lib/cortexa9hf_neon_Release/liboatpp.a
(replace the path with your actual path, of course)
I got confused and didn't realize "file" was a command.
liboatpp.a: current ar archive
Mmmmh that doesn't seem to say a lot.
What about
objdump -a path/to/liboatpp.a?
I get for example
Pattern.cpp.o: tiedostomuoto elf64-x86-64
rw-r--r-- 0/0 417832 Jan 1 02:00 1970 Pattern.cpp.o
Pattern.cpp.o: tiedostomuoto elf64-x86-64
rw-r--r-- 0/0 417832 Jan 1 02:00 1970 Pattern.cpp.o
Processor.cpp.o: format de fichier elf32-i386
rw-r--r-- 0/0 190588 Jan 1 01:00 1970 Processor.cpp.o
rw-r--r-- 0/0 190588 Jan 1 01:00 1970 Processor.cpp.o
Je comprends.
This is the important thing: elf32-i386
So you didn't cross-compile it for (32bit) arm, you just built it for 32bit x86 architecture.
Ok so at least we know why it doesn't work now.
Yeah. So you have to somehow convince cmake to use your cross-compiling (for armhf) toolchain instead of your native (x86_64) one. Maybe the line
source /opt/phytec-yogurt/BSP-Yocto-i.MX6-PD18.1.1/environment-setup-cortexa9hf-neon-phytec-linux-gnueabi should have done something like that, but apparently it didn't.
Hi, I'm trying to somehow get into Oat++, but I am honestly quite struggling with the documentation. Oat++ uses macros a lot for a C++ library (maybe even more than what I am used to from C where one does not have templates etc.), and at least to me function of many of them is far from obvious without looking into the code.
My point is that it would REALLY help if the documentation provided at least a high-level overview of how does the Oat++ macro system work and what do the macros actually do (mainly in the ORM/DTO and DI parts).
The macros are used throughout the examples, but AFAIK it isn't explained anywhere what they do.
Hello @mmn:matrix.org ,
The macros are used throughout the examples, but AFAIK it isn't explained anywhere what they do.
You can find docs on ORM, DTO, and other oatpp components here on the website:
- DTO - https://oatpp.io/docs/components/dto/
- ORM - https://oatpp.io/docs/components/orm/
- ApiController - https://oatpp.io/docs/components/api-controller/
- ApiClient - https://oatpp.io/docs/components/api-client/
If you feel that those docs aren't enough - please file an issue on Github - in oatpp website repo - https://github.com/oatpp/website
Also, please feel free to ping me here in case you need some deeper technical details on how those macros work.
//My client class
class VoucherClient : public oatpp::web::client::ApiClient
{
#include OATPP_CODEGEN_BEGIN(ApiClient)
API_CLIENT_INIT(VoucherClient)
API_CALL_ASYNC("POST", "/", getRoot)
API_CALL("POST", "/connect", connect, BODY_STRING(String, ip))
#include OATPP_CODEGEN_END(ApiClient)
};
//My API call function :
void funcCall(shared_ptr<VoucherClient> client)
{
cout << "[Connect] Calling the server..." << endl;
auto data = client->connect("127.0.0.1")->readBodyToString(); //Crash dans le thread
OATPP_LOGD("CLIENT", "[connect] data='%s'", data->c_str());
}
//My run function :
void run()
{
cout << "Creating objectmapper" << endl;
auto objectMapper = oatpp::parser::json::mapping::ObjectMapper::createShared();
cout << "Creating requestexecutor" << endl;
auto requestExecutor = createOatppExecutor();
cout << "Creating client" << endl;
auto client = VoucherClient::createShared(requestExecutor, objectMapper);
std::thread th(client);
}
//My main function :
int main()
{
oatpp::base::Environment::init();
printHelp();
run();
oatpp::base::Environment::destroy();
cout << "Press any key to close the program" << endl;
_getch();
return 0;
}