Percy wrote:
> I tried all that, ran Visual Studio as Administrator and this is what I got
> as the first error when I compiled:
> 1>fl_read_image.cxx
> 1>Fl_Progress.cxx
> 1>Fl_Preferences.cxx
> 1>..\..\src\Fl_Preferences.cxx(85) : fatal error C1021: invalid preprocessor
> command 'warning'
Hmm, that does sound wrong -- like one of the devs added a "#warning"
directive to the source code, but didn't #ifdef it out for the VS
compiler.
This must be recent.
You can probably solve that by just deleting that line (line 85) in the
src\Fl_Preferences.cxx file.. the warning is not needed to build.
> There was also these at the start:
> 1>------ Build started: Project: fltk, Configuration: Debug Win32 ------
> 2>------ Build started: Project: fltkimages, Configuration: Debug Win32 ------
> 2>Compiling...
> 3>------ Build started: Project: jpeg, Configuration: Debug Win32 ------
> 1>fltk : warning PRJ0009 : Build log could not be opened for writing.
> 1>Make sure that the file is not open by another process and is not
> write-protected.
> 3>jpeg : warning PRJ0009 : Build log could not be opened for writing.
> 3>Make sure that the file is not open by another process and is not
> write-protected.
> 4>------ Build started: Project: libpng, Configuration: Debug Win32 ------
> 4>libpng : warning PRJ0009 : Build log could not be opened for writing.
> 4>Make sure that the file is not open by another process and is not
> write-protected.
>
> security issues... which is odd since it is on the local drive and I'm
> running as the administrator.
These are apparently not stopping the build since this is
just the 'clean' stage. But if you get similar errors during
the build stage, then it definitely needs to be solved first.
Files can be un-writeable even to administrator if they're
readonly, or if the ACLs are really messed up.
Check if the files are read-only, and if so, change it through the GUI
then *double check* to make sure the GUI really did change it; watch
out for:
<http://www.techsupportforum.com/microsoft-support/windows-xp-support/98060-stuborn-non-changable-read-only-folder.html>
then try again.
read-only files can be fixed from DOS with the 'attrib' command,
and messed up ACLs can be fixed with the DOS 'cacls' command.
Or you can use the GUI.. but I don't always trust the GUI.
For help with the DOS commands, see 'attrib /?' and 'cacls /?')
Sometimes files end up read-only if copied from eg. a cdrom
or some other read-only/write protected medium.
Did you try renaming the dir away and re-extracting from the tar
file? Curious what steps you're using to unpack the tar.. normally
the steps are:
1) Download the tar.gz from the fltk.org website
2) Use Winzip to unzip the gzipped tar
3) Build
IIRC, one of Microsoft's "built in" unzippers (Vista? Win7? One of
those..)
had a bug where it would unzip everything 'read only', so you had to
manually
disable the read-only flag from the entire extracted directory after
unzipping.
_______________________________________________
fltk mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk
