The whole thing goes like this:
Set Freeamp as active project when you first compile.
Then, if you feel like hacking the freeamp ui (the user interface) you set
freeampui as active project and freeamp.exe as executable to run. If you
feel like hacking other part of freeamp, set that other part as active.
To freeamp team - why leave "MakeTheme" as active when checking into CVS?
MakeTheme has zlib dependency because it compresses theme when making it.
Ofcourse zlib should be added as dependency to it (if visual studio does
not object).
Note that you will need about 150 MB of free space on disk to compile. Be
sure that you don't run out of free space.
At 11:53 5/28/00 -0500, you wrote:
>> trying to compile the freeamp project I get this error: (of
>> course I dont
>> have a correct configuration of my workspace, can you tell me
>> how can I do a
>> correct cnfiguration, about Tools, Project, Build, etc) please.
>
>Victor,
>
>Try right clicking on the FreeAmp project and setting it to the active
>project and then to a Build All. I'm not sure right off if the MakeTheme
>project has a depenency on zlib (don't have the code open right now), but
>i'm very sure FreeAmp does, and then you can set MakeTheme to be the active
>project and compile it.
>
>mike
>
>_______________________________________________
>[EMAIL PROTECTED]
>http://www.freeamp.org/mailman/listinfo/freeamp-dev
>
>
--
Valters "WaTT" Vingolds
... in order to succeed you have to learn to think of yourself as of a
product.
_______________________________________________
[EMAIL PROTECTED]
http://www.freeamp.org/mailman/listinfo/freeamp-dev
