This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

1

MilkyTracker Support / Re: compiling errors

« on: February 05, 2009, 07:31:41 »

ok this is some VisualC++ express edition shit, because I just took this to another machine and compiled it straight out of the box with no problems. I guess I got to dig up my old MSDN box and find my copy of devstudio 2005.

2

MilkyTracker Support / Re: compiling errors

« on: February 05, 2009, 06:18:14 »

So did you try with the link I provided? Does it work now?

nope. It failed at first looking for afxres.h. I pointed it to the platform SDK and got this.


http://themysterioush.net/imhoste/newErrorlog.txt

3

MilkyTracker Support / Re: compiling errors

« on: February 05, 2009, 00:39:10 »

I gotta get home from work first.

4

MilkyTracker Support / Re: compiling errors

« on: February 04, 2009, 17:46:22 »

There must be something wrong with your includes or the directory structure of your workspace. The compiler is obviously missing header files right at the very beginning.
Are you new to c/c++? It should be fairly easy to resolve these issues.

This compiles straight away with vs 2005:
http://peter.nxbone.net/milkytracker-0.90.zip

Unpack, load solution file, press compile...

not particularly new, but I'm self taught and tend to work entirely within embedded microcontroller type projects so we rarely deal with projects this big. Plus I don't use visual studio too much. But thanks for all the help!

5

MilkyTracker Support / Re: compiling errors

« on: February 04, 2009, 04:17:24 »

Here is a giant log!

http://themysterioush.net/imhoste/CompileLog.txt

6

MilkyTracker Support / Re: compiling errors

« on: February 03, 2009, 17:18:50 »

WinXP SP2 is the target. I tried getting rid of the winCE and Carbon directories and I endend up with the compiling messing up somewhere else having to do with PPUI stuff in Tracker.h.

you know I just realized that I might have put the winCE "Missing" directory in there, which might be causing name conflicts.

Are you trying to compile for Windows or Windows CE?

7

MilkyTracker Support / Re: compiling errors

« on: February 02, 2009, 23:41:04 »

you know I just realized that I might have put the winCE "Missing" directory in there, which might be causing name conflicts.

8

MilkyTracker Support / Re: compiling errors

« on: February 02, 2009, 23:28:19 »

afxres.h Dunno what's the problem here, but I can tell you that MilkyTracker has got minimal Windows header dependencies.

it was something in one of the RTAudio files if I recall correctly. I think I'm going to purge everything and try again.

Probably some name clash or something. MilkyTracker compiles right out of the box even with the oldest compilers.

perhaps it's the newness of the compiler that is the problem. Do you know who made the project file for Visual studio that's distributed with the source, maybe there is something wierd going on in there that's telling it to find the MFCs or something.

9

MilkyTracker Support / Re: compiling errors

« on: February 02, 2009, 21:06:40 »

Have you checked whether the include paths are correct?

well at first it wasn't locating the platform SDK and freezing up on afxres.h, so I added that to the include path. It's not complaining about not being able to find something, just about all of these PPUI functions needing casts. Is this likely because of a missing header? If so which header?

10

MilkyTracker Support / compiling errors

« on: February 02, 2009, 04:54:02 »

I'm trying to compile Milkytracker on WinXP under visualstudio. I get a whole lot of errors.

most of them some version of this

error C2664: 'PPCheckBox::PPCheckBox(pp_int32,PPScreen *,EventListenerInterface *,PPPoint,bool)' : cannot convert parameter 3 from 'SectionOptimize *const ' to 'EventListenerInterface *'
        Types pointed to are unrelated; conversion requires reinterpret_cast, C-style cast or function-style cast

as well there are several ppui related errors in tracker.h.

does anyone know what is going on?