b2settings.h <cassert> not found

Hi all,

I got a project using Box2D and it works fine when I test it on the simulator.
But when I try to plug in a real device with correct provision and certificate.
I get an error about b2settings.h that it doesn’t know =/
Found a lot of problems on internet for cocos2d-iphone but not for -x
Anyone got any idea?

ty in advance,

Xep

What’s the problem?

Well,

When I try to build/run for simulator everything works fine and build succeeded.
But when I plug in a real device and try to build it fails because it says. unknown in b2Settings.h =/
So I can’t test it on a real device :S
Really weird. Any idea?

xep

Android or iOS?
What’s the version of cocos2d-x?
Did you test HelloWorld?
What’s the step you did to run on device?

It’s for iOS.

I never tested the Helloworld with my provision keys.
I got the latest version.
And I just Clean and Build. And it works perfectly on simulator.
But when I plug in my device and I press build it gives the error =/
Really weird.

xep

Seppe R wrote:

It’s for iOS.
>
I never tested the Helloworld with my provision keys.
I got the latest version.
And I just Clean and Build. And it works perfectly on simulator.
But when I plug in my device and I press build it gives the error =/
Really weird.
>
xep

EDIT: Randomly got the error on the simulator now to =/

Did you use template to create you project?
And did you select the template for cocos2d-x + box2d?

Yes I started my project with the template with Box2D.
I’m going to try the helloworld with my provision keys now and see if that works.

EDIT: Well I tried a new project again and it works =/
And then I start changing the files and adding my classes and it works to :slight_smile:
So now I can run my project on the device.
But now I get the error on simulator build =/ oh god .

Am I the only one with this problem?
When I start a new project it works, but then when I do a clean or something, the error is back
and doesn’t go away. And I get frustrated of starting a project over and over again =/

I just meet the same problem, and solve it with a really stupid way:

make sure every files using .mm extension
(which means you have to change “.m” to “.mm”~~)

Good luck

coco wang wrote:

I just meet the same problem, and solve it with a really stupid way:
>
make sure every files using .mm extension
(which means you have to change “.m” to “.mm”~~)
>
Good luck

Yeah I found that also everywehere on the internet but I fixed my problem and it’s even more stupid.
I had a class named Block.cpp which messed up with a block class of ios =/ Really lame searching for weeks for that stupid solution.

:slight_smile: So people don’t name your class “Block” lol

cheers