[webkit-dev] Build errors

[drewtenn at yahoo.com]

I looked in WebCoreGenerated and found the build log.

I saw some errors in the log relating to an invalid switch, but I can't tell which it's referring to.

/cygdrive/c/Users/DTENNE~1/WebKit/WE1674~1/include/JavaScriptCore/create_hash_table /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSDOMWindowBase.cpp -n WebCore > JSDOMWindowBase.lut.h
Creating hashtable for /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSDOMWindowBase.cpp
/cygdrive/c/Users/DTENNE~1/WebKit/WE1674~1/include/JavaScriptCore/create_hash_table /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSRGBColor.cpp -n WebCore > JSRGBColor.lut.h
/cygdrive/c/Users/DTENNE~1/WebKit/WE1674~1/include/JavaScriptCore/create_hash_table /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSWorkerContext.cpp -n WebCore > JSWorkerContext.lut.h
Creating hashtable for /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSRGBColor.cpp
perl -I /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/scripts /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/scripts/generate-bindings.pl --include dom --include html --include css --include page --include xml --include svg --outputDir . --defines "ENABLE_DATABASE ENABLE_DOM_STORAGE ENABLE_ICONDATABASE ENABLE_OFFLINE_WEB_APPLICATIONS ENABLE_XPATH ENABLE_SVG ENABLE_SVG_ANIMATION ENABLE_SVG_FONTS ENABLE_SVG_FOREIGN_OBJECT ENABLE_SVG_AS_IMAGE ENABLE_SVG_USE ENABLE_VIDEO LANGUAGE_JAVASCRIPT" --generator JS /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/inspector/JavaScriptCallFrame.idl
Creating hashtable for /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/bindings/js/JSWorkerContext.cpp
bison -d -p cssyy /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/CSSGrammar.y -o CSSGrammar.cpp
if sort /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/CSSPropertyNames.in /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/SVGCSSPropertyNames.in | uniq -d | grep -E '^[^#]'; then echo 'Duplicate value!'; exit 1; fi
touch CSSGrammar.cpp.h
Invalid switch.
touch CSSGrammar.hpp
cat /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/CSSPropertyNames.in /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/SVGCSSPropertyNames.in > CSSPropertyNames.in
echo '#ifndef CSSGrammar_h' > CSSGrammar.h
echo '#define CSSGrammar_h' >> CSSGrammar.h
perl "/cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/makeprop.pl"
cat CSSGrammar.cpp.h CSSGrammar.hpp >> CSSGrammar.h
echo '#endif' >> CSSGrammar.h
rm -f CSSGrammar.cpp.h CSSGrammar.hpp
# Lower case all the values, as CSS values are case-insensitive
perl -ne 'print lc' /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/CSSValueKeywords.in /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/css/SVGCSSValueKeywords.in > CSSValueKeywords.in
gperf -CDEot -L ANSI-C -k '*' -N findColor -D -s 2 /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/platform/ColorData.gperf > ColorData.c
if sort CSSValueKeywords.in | uniq -d | grep -E '^[^#]'; then echo 'Duplicate value!'; exit 1; fi
gperf -CEot -L ANSI-C -k "*" -N findDoctypeEntry -F ,PubIDInfo::eAlmostStandards,PubIDInfo::eAlmostStandards /cygdrive/c/Users/DTENNE~1/WebKit/WebCore/html/DocTypeStrings.gperf > DocTypeStrings.cpp
Duplicate value!
make: *** [CSSValueKeywords.h] Error 1
make: *** Waiting for unfinished jobs....



--- On Sat, 11/15/08, Julien Chaffraix <julien.chaffraix at gmail.com> wrote:

> From: Julien Chaffraix <julien.chaffraix at gmail.com>
> Subject: Re: [webkit-dev] Build errors
> To: drewtenn at yahoo.com
> Cc: webkit-dev at lists.webkit.org
> Date: Saturday, November 15, 2008, 9:02 AM
> Hi,
> 
> On Fri, Nov 14, 2008 at 6:19 PM, drewtenn at yahoo.com
> <drewtenn at yahoo.com> wrote:
> > I'm trying to successfully build WebKit using
> Visual Studio 2005 but I keep getting compile errors.
> >
> > SVGElement.h includes SVGNames.h but I don't see
> SVGNames.h in any directory.
> > No such file for HTMLNames.cpp
> >
> > My SVN checkout succeeded so I'm not sure why
> I'm running into this.
> 
> Those 2 files are automatically generated by make_names.pl
> (in
> WebCore/dom/) during the build process.
> 
> Check whether they are present in your build directory. If
> not, your
> build logs should point out what is failing (you can try
> posting it
> here in case someone knows what the problem is).
> 
> Hope it helps,
> 
> Julien