Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

How to use capsin in Visual Studio 2017 #1

Open
al-sabr opened this issue May 18, 2017 · 2 comments
Open

How to use capsin in Visual Studio 2017 #1

al-sabr opened this issue May 18, 2017 · 2 comments

Comments

@al-sabr
Copy link

al-sabr commented May 18, 2017

Hi I would like to know how can I use your project inside of another project within Visual Studio 2017.
I get 2 error with the macros that you defined

#include "caspin\caspin_base.h"
#include "caspin\cspNativePackage.h"
#include "caspin\cspOutputListener.h"
#include "caspin\cspSystem.h"
#include "caspin\cspVmCore.h"

using namespace std;
using namespace avmplus;

image

image

image

Can you help me?

@drywolf
Copy link
Owner

drywolf commented Jun 5, 2017

Hi, sorry for the late reply but somehow this issue got past me in my github notifications.

I haven't tried to build caspin since I made those last commits (2011), so it probably would take quite some effort to get it working after all this time. Also tamarin is no longer developed or used by mozilla, so I'd heavily recommend to reconsider using it for anything but experimentation today.

As an alternative I would suggest looking into embedding Node.js instead, the ecosystem & community is already huge and growing everyday.

If you still need to get caspin running, could you confirm that those errors that you show also are reported by the compiler ? Intellisense has become better over all those years, but you better be sceptical to trust those red squiggly lines too much 😆

@drywolf
Copy link
Owner

drywolf commented Jun 5, 2017

Also, as far as I remember there were some breaking API changes in Tamarin at the time I made this commit 96436b4 ... which tells that you would still need to implement those changes into caspin to make it work again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants