example-basic, breaks at: core = WebCore::Initialize(config);

[rwebber]

with the latest Awesomium sdk installed, and OF 0.9.3
I can not get example-basic to run (all linking is good, checked 3 times)
Trying to build debug it breaks at ofxAwesomiumPlus.cpp line 372
core = WebCore::Initialize(config);

build for Release gives: Lnk2001 errors ( swear all linking vars are setup correctly )

sorry of this isn't the right place for this.

[razvanilin]

I don't think I tried it with the latest OF so it might break. I will check
it as soon as I can, but I'm currently on holiday so it might take a bit of
time.

On Thu, 26 May 2016, 21:12 rwebber, [email protected] wrote:

with the latest Awesomium sdk installed, and OF 0.9.3
I can not get example-basic to run (all linking is good, checked 3 times)
Trying to build debug it breaks at ofxAwesomiumPlus.cpp line 372
core = WebCore::Initialize(config);

build for Release gives: Lnk2001 errors ( swear all linking vars are setup
correctly )

sorry of this isn't the right place for this.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#3

[rwebber]

greatly appreciated. I'm pretty new with OF

[rwebber]

wanted to let you know, that the issue seemed to be some corrupt file from the SDK.
After some messing about, replacing the required files in the build/bin seems to have fixed the issue.
I have this running nicely in OF 0.9.3 on windows.

I would like to know what your plans for ofxAwesomiumPlus::getState() is?
I could really use something here, and may be able to help out.
For now I am using IsLoading() but it doesn't fully serve my purpose.
Combining IsDocumentReady() and IsLoading() plus some others into a State is what I am imagining..
Let me know your thoughts and I can play with it.

[razvanilin]

Glad to hear that you managed to get it working.

My thoughts for getState() is to remove it completely and replace it with
another method described in the other opened issue #2 . So that state doesn't
actually describe the state (ready, loaded) of the page.

You can, for example, listen for the state of the DOM in javascript and
when the page is fully loaded, set the state to "LOADED" or something and
then listen for that in the OF app.

On Tue, 31 May 2016, 02:53 rwebber, [email protected] wrote:

wanted to let you know, that the issue seemed to be some corrupt file from
the SDK.
After some messing about, replacing the required files in the build/bin
seems to have fixed the issue.
I have this running nicely in OF 0.9.3 on windows.

I would like to know what your plans for ofxAwesomiumPlus::getState() is?
I could really use something here, and may be able to help out.
For now I am using IsLoading() but it doesn't fully serve my purpose.
Combining IsDocumentReady() and IsLoading() plus some others into a State
is what I am imagining..
Let me know your thoughts and I can play with it.

—
You are receiving this because you commented.

Reply to this email directly, view it on GitHub
#3 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AFGEccOf1QFPU1A436kP68XZBt9Zqu4gks5qG5SHgaJpZM4In6Le
.

[rwebber]

I didn't see the other issue posted.
I saw the Domready function in the Awesomium Api, seems very useful.

SO, I spoke too soon.
I can build in debug, but release is giving me the following error:

Severity Code Description Project File Line Suppression State
Error LNK2001 unresolved external symbol "__declspec(dllimport) public: __thiscall Awesomium::WebString::~WebString(void)" (_imp??1WebString@Awesomium@@QAE@XZ) webviewUtility C:\OF\of_v0.9.3_vs_release\apps\myApps\webviewUtility\main.obj 1

After this there are many more LNK2001 unresolved external symbol errors, in the ofxAwesomeiumPlus.odj
Seems that something is not being linked in release.
Any insight into this would be greatly appreciated.

note: I also found that I need to #include "ofxAwesomiumPlus.h" after most other headers. Otherwise a DWORD error is given and the build fails (in debug). Perhaps something for the readme.

[rwebber]

Again, I'm being such a OF noob. Sorry..
I messed up the linking, in that I didn't get it done for both release and debug (missed that entirely... that won't happen again ;)
I really appreciate this addon... thanks for the great work.

[razvanilin]

Haha, don't worry I fell for that too one time :)

Thanks for pointing the DWORD error to me, I will give it a go soon and make sure I will include it in the readme. I am back home now and I might have a bit of free time to improve the addon a bit.

[rwebber]

Simplest method to repeatably cause the DWORD error, is to add:
#include "ofxOsc.h"
after including ofxAwesomiumPlus.h

Other plugins will cause this issue, but this is the one I confirmed the fix for. (load ofxOsc.h first)
additionally, you might (I have made this change, haven't confirmed its 100% necessary) need to declare the ofxAwesomiumPlus object before the other public stuff.