cabasa icon indicating copy to clipboard operation
cabasa copied to clipboard

can't build with hexlog

Open sonygod opened this issue 4 years ago • 18 comments

Error: ./src/hex/log/LoggerConfig.cpp: In member function ‘virtual hx::Val hex::log::LoggerConfig_obj::__Field(const String&, hx::PropertyAccess)’:

sonygod avatar Jan 29 '20 02:01 sonygod

@sonygod C++ target is broken for hexlog version I installed.

I will take a look.

Btw, I just pushed another commit for Wasp

darmie avatar Jan 29 '20 09:01 darmie

@sonygod I have fixed the hexlog issue

Install the alpha version

haxelib install hexlog 1.0.0-alpha.7

darmie avatar Jan 29 '20 09:01 darmie

still got nothing trace or file generate?

have you test your project and then push into github?

sonygod avatar Jan 30 '20 04:01 sonygod

image

sonygod avatar Jan 30 '20 04:01 sonygod

@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.

darmie avatar Jan 30 '20 06:01 darmie

oh....

which target have you test before?

sonygod avatar Jan 30 '20 07:01 sonygod

C# and Java

darmie avatar Jan 30 '20 07:01 darmie

@sonygod I just made a new PR merge. You can pull from master and run it again for C++ target.

C++ target now working

darmie avatar Jan 30 '20 08:01 darmie

I'll take a look later..

sonygod avatar Jan 30 '20 09:01 sonygod

$RY A)4LC7T~%FUQ6X@HC8E

there are still something error ,maybe platform issue?

ubuntu 18.04

@darmie

sonygod avatar Jan 30 '20 11:01 sonygod

@sonygod please update your version of Wasp

darmie avatar Jan 30 '20 13:01 darmie

after update.it's seem only

call_fib(raw5);

not work.

erveryhing seem ok

Y05UZRA}L4EK%18)V2~6X

sonygod avatar Jan 30 '20 13:01 sonygod

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 .

darmie avatar Jan 30 '20 16:01 darmie

are you going to support wasm build by hxcpp?

the current version I did test seems not support hxcpp's wasm .

wasm.zip

sonygod avatar Jan 31 '20 09:01 sonygod

@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.

darmie avatar Jan 31 '20 09:01 darmie

I jsut use hxcpp defalut toolchain.xml with emcc ,

is this not Binaryen?

sonygod avatar Jan 31 '20 09:01 sonygod

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.

darmie avatar Jan 31 '20 10:01 darmie