cabasa
cabasa copied to clipboard
can't build with hexlog
Error: ./src/hex/log/LoggerConfig.cpp: In member function ‘virtual hx::Val hex::log::LoggerConfig_obj::__Field(const String&, hx::PropertyAccess)’:
@sonygod C++ target is broken for hexlog version I installed.
I will take a look.
Btw, I just pushed another commit for Wasp
@sonygod I have fixed the hexlog issue
Install the alpha version
haxelib install hexlog 1.0.0-alpha.7
still got nothing trace or file generate?
have you test your project and then push into github?
I have not tested Cabasa with cpp, I have only tested Wasp with cpp.
On Thu, 30 Jan 2020, 05:50 Mr zhan, [email protected] wrote:
[image: image] https://user-images.githubusercontent.com/748320/73420893-0ac72980-435f-11ea-9730-18fcfd8cdc55.png
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/darmie/cabasa/issues/1?email_source=notifications&email_token=AAGPBASWNFQDN4W4RKC4VNTRAJMATA5CNFSM4KM5X6AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKJVSLI#issuecomment-580081965, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGPBAUAYECF5JJ5CD7BVU3RAJMATANCNFSM4KM5X6AA .
@sonygod use build.hxml
In test.hxml
I was trying to use a new C++ and Hashlink binder which is not working.
Apologies for the confusion.
Also please note that C++ version of Cabasa doesn't work yet.
oh....
which target have you test before?
C# and Java
@sonygod I just made a new PR merge. You can pull from master and run it again for C++ target.
C++ target now working
I'll take a look later..
there are still something error ,maybe platform issue?
ubuntu 18.04
@darmie
@sonygod please update your version of Wasp
after update.it's seem only
call_fib(raw5);
not work.
erveryhing seem ok
Yes I am aware. I commented it out because I am still investigating it.
On Thu, 30 Jan 2020, 14:35 Mr zhan, [email protected] wrote:
after update.it's seem only
call_fib(raw5);
not work.
erveryhing seem ok
[image: Y05UZRA}L4EK%18)V2~6X] https://user-images.githubusercontent.com/748320/73454145-71246a00-43a8-11ea-83b3-cd2014ab93fc.png
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/darmie/cabasa/issues/1?email_source=notifications&email_token=AAGPBASHKBKZ57HOUDIA3R3RALJS7A5CNFSM4KM5X6AKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKK76UI#issuecomment-580255569, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAGPBAUT6XFMO6HXTUXLAF3RALJS7ANCNFSM4KM5X6AA .
are you going to support wasm build by hxcpp?
the current version I did test seems not support hxcpp's wasm .
@sonygod Cabasa is designed to support the MVP version of wasm, it depends on what tool you used to compile hxcpp code to wasm. I suggest you use Binaryen.
I jsut use hxcpp defalut toolchain.xml with emcc ,
is this not Binaryen?
I don't know. I will focus on hxcpp specifics when I have much time. Right now, I use wasm builds from WebAssembly Studio for my tests.