[pgcalid]

I'm attempting to compile XBMC for Windows and I'm getting the following error:

error C2512: 'CFileItem' : no appropriate default constructor available

I actually get a number of errors but I believe they all stem from the above error.

I'm using Visual Studio 2008 and I'm on Vista.

I did a get of the source, installed the DirectX SDK and add the include and library directx paths to my solution.

This is happening during the compile of the XBMC project, the guilib, libPlatinum and UnrarXLib projects all compile with no errors.

Am I missing something obvious?

[jmarshall]

We'd need more information - why not post your build log on pastebin or similar?

[pgcalid]

Posted

http://pastebin.com/m46a6a59e

The problems start with GUIInfoManager.cpp

[jmarshall]

Try adding a #include "FileItem.h" somewhere up the top there. Looks like an include order problem.

EDIT: Hmm, nope - FileItem.h is included in PlayList.h which is included in GUIInfoManager.cpp

The default constructor is clearly present in FileItem.h/cpp.

Which branch do you have checked out?

[pgcalid]

I'm not sure which branch to be honest. I used the instructions from

HOW-TO compile XBMC for Windows from source code in the XBMC wiki.

I did an SVN get using:

https://xbmc.svn.sourceforge.net/svnroot...xport/XBMC

[CrashX]

What solution file are you using ?

[pgcalid]

I'm using:

XBMC for Windows.sln

in the project\VS2008Express directory

[WiSo]

The only thing I noticed is that we call CFileItem without the brackets:
m_currentFile = new CFileItem;

IIRC I have this seen before but in this case it works fine for me.

[pgcalid]

I noticed that to. I put the brackets () in but had the same result.

[pgcalid]

Well this seems to have worked itself out. So thanks to whoever fixed it.

However it would be kind of nice to know what the problem is, if anyone does know. As others have commented, it looked it should have been fine the way it was.

[spiff]

and fyi

m_currentFile = new CFileItem;
and
m_currentFile = new CFileItem();

are exactly the same

[WiSo]

Thanks and good to know
but IIRC that causes once problems on Windows. Maybe I mix it with another problem.