[jamming] jam and Fitz-muPDF

Pranay Pramod pranay.pramod at gmail.com
Tue Jul 10 01:29:35 PDT 2007


Thanks Craig and Dean!

I was getting most of the errors because of misplaced library headers.
Now, however, I still have three targets failing while linking...

----------------------------------------------------------------
Compiler is GCC with Mingw
Building RELEASE target
...found 352 target(s)...
...updating 3 target(s)...
Link build\release\pdftool.exe

gcc  -o build\release\pdftool.exe  build\release\pdftool.o
build\release\libmupdf.a build\release\libfonts.a build\release\libraster.a
build\release\libworld.a build\release\libstream.a build\release\libbase.a
-Lc:/msys/1.0/local/lib -lfreetype -ljpeg -lz -lm

...failed Link build\release\pdftool.exe ...
Link build\release\apparition.exe

gcc  -o build\release\apparition.exe  build\release\winmain.o
build\release\winres.o build\release\libpdfapp.a build\release\libmupdf.a
build\release\libfonts.a build\release\libraster.a build\release\libworld.a
build\release\libstream.a build\release\libbase.a -Lc:/msys/1.0/local/lib
-lfreetype -ljpeg -lz -lm -lgdi32 -lcomdlg32 -mwindows

...failed Link build\release\apparition.exe ...
Link build\release\npmupdf.dll

gcc -shared -Wl,--kill-at -o build\release\npmupdf.dll
build\release\npwin.o build\release\moz_winres.o build\release\moz_main.o
build\release\libmupdf.a build\release\libfonts.a build\release\libraster.a
build\release\libworld.a build\release\libstream.a build\release\libbase.a
-Lc:/msys/1.0/local/lib -lfreetype -ljpeg -lz -lm -lgdi32

...failed Link build\release\npmupdf.dll ...
...failed updating 3 target(s)...

c:\mingw\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot
find -lfreetype
collect2: ld returned 1 exit status
c:\mingw\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot
find -lfreetype
collect2: ld returned 1 exit status
c:\mingw\bin\..\lib\gcc\mingw32\3.4.2\..\..\..\..\mingw32\bin\ld.exe: cannot
find -lfreetype
collect2: ld returned 1 exit status

-----------------------------------------------------------------
my Jamrule says

if $(OS) = MINGW
{
	FREETYPECC ?= -Ic:/msys/1.0/local/include
-Ic:/msys/1.0/local/include/freetype2 ;
	FREETYPELD ?= -Lc:/msys/1.0/local/lib -lfreetype ;
}

FREETYPECC ?= "`freetype-config --cflags`" ;
FREETYPELD ?= "`freetype-config --libs`" ;

where do i look for this missing -lfreetype??

Thanks!
Pranay


On 7/9/07, Craig Allsop <cjamallsop at gmail.com> wrote:
>
> Hi. What does gcc say is the problem, are the errors before this line?
>
> Craig.
>
> On 7/9/07, Pranay Pramod <pranay.pramod at gmail.com> wrote:
> > Thnks again Dean!
> >
> > setting the OS variable to MINGW updated many of the targets.
> > However I still have failed targets like:
> >
> > -----------------------------------------
> > gcc -c -o build\release\filt_dctd.o -Wall -Ic:/msys/1.0/local/include
> > -Ic:/msys/1.0/local/include/freetype2 -std=gnu99 -DHAVE_C99
> > -DWIN32 -O3  -DNEED_GETOPT -DNEED_STRLCAT -DNEED_STRLCPY -DNEED_STRSEP
> > -Istream -Iinclude  stream\filt_dctd.c
> >
> > ...failed Cc build\release\filt_dctd.o ...
> > Cc build\release\filt_dcte.o
> >
> > HexDump build\release\Dingbats.c
> >  xxd -i fonts\Dingbats.cff | sed -e 's/unsigned/const unsigned/' >
> > build\release\Dingbats.c
> > ...failed HexDump build\release\Dingbats.c ...
> > ----------------------------------------
> >
> > I have installed a window based VIM and assumed it has xxd but i think
> am
> > wrong.(hexDump failures)
> > I am tryin to debug things but still at sea.
> > As instructed in readme, I have installed the dependency libraries like
> > libjpeg,zlib but how are they "recognized"?  they are installed under
> > C:\Program Files\GnuWin32.
> > Do i need to modify the jamrule for this?
> > Sorry for the ignorant and longer mail :)
> >
> > Regards,
> > Pranay
> >
> > On 7/8/07, tribble at deantribble.com <tribble at deantribble.com> wrote:
> > >
> > >
> > > The debugging options in Jam are extremely helpful.  When debugging, I
> > often dump "jam -d8" into a file and search it in emacs.  In this case,
> the
> > OS variable is set to "NT", and that's not one of the supported OS
> options
> > in the Jamrules file.  Try setting your OS shell variable to MINGW.
> > >
> > >
> > > Quoting Pranay Pramod <pranay.pramod at gmail.com >:
> > >
> > > > Hi Dean,
> > > >
> > > > I am attaching the build failure log again.
> > > > Build fails for several targets like (only few ones am pasting):
> > > >
> > > > -----------------------------------
> > > > Compiler is GCC with Mingw
> > > > OS 'NT' not known by build system.
> > > > If you get errors, please edit Jamrules.
> > > > Building RELEASE target
> > > > ...found 436 target(s)...
> > > > ...updating 139 target(s)...
> > > > Cc build\release\base_cpudep.o
> > > >
> > > > gcc -c -o build\release\base_cpudep.o -Wall `freetype-config
> --cflags`
> > > > -std=c89 -O3   -Ibase -Iinclude  base\base_cpudep.c
> > > >
> > > > ...failed Cc build\release\base_cpudep.o ...
> > > > Cc build\release\base_error.o
> > > > .
> > > > .
> > > > .
> > > > gcc -c -o build\release\crypt_arc4.o -Wall `freetype-config
> --cflags`
> > > > -std=c89 -O3   -Istream -Iinclude  stream\crypt_arc4.c
> > > >
> > > > ...failed Cc build\release\crypt_arc4.o ...
> > > > Cc build\release\crypt_crc32.o
> > > > .
> > > > .
> > > > gcc -c -o build\release\obj_parse.o -Wall `freetype-config --cflags`
> > > > -std=c89 -O3   -Istream -Iinclude  stream\obj_parse.c
> > > >
> > > > ...failed Cc build\release\obj_parse.o ...
> > > > Cc build\release\obj_print.o
> > > > ..
> > > >
> > > > gcc -c -o build\release\pdfapp.o -Wall `freetype-config --cflags`
> > -std=c89
> > > > -O3   -Iapps\common -Iinclude  apps\common\pdfapp.c
> > > >
> > > > ...failed Cc build\release\pdfapp.o ...
> > > > ...skipped libpdfapp.a for lack of libpdfapp.a(pdfapp.o)...
> > > > Cc build\release\pdftool.o
> > > >
> > ------------------------------------------------------------------
> > > >
> > > > ~Pranay
> > > >
> > > > On 7/8/07, Dean Tribble <tribble at e-dean.com> wrote:
> > > >>
> > > >> FYI I saw the Jamrules but no log file attached.
> > >
> > > >>
> > > >> On 7/7/07, Pranay Pramod <pranay.pramod at gmail.com> wrote:
> > > >>
> > > >>> Hi All,
> > > >>>
> > > >>> I am trying to compile the fitz-muPDF source.
> > > >>> As instructed in the readme, I installed the 3rd party
> dependencies
> > and
> > > >>> am using MYSYS-mingW on my XP machine
> > > >>>
> > > >>> However the build is failing.
> > > >>> I am new to jam and unable to diagnose the problem.
> > > >>> Please guide me on this.
> > > >>> I am attaching the build failure log and the Jamrules.
> > > >>>
> > > >>> thanking you,
> > > >>> Pranay
> > > >>>
> > > >>> On 7/7/07, Pranay Pramod < pranay.pramod at gmail.com> wrote:
> > > >>> >
> > > >>> > Hi All,
> > > >>> > I am a newbie to jam tool.
> > > >>> >
> > > >>> > Basically I am compiling muPDF (an open source PDF parser).
> > > >>> > For that, i already have installed MSYS and minGW.
> > > >>> >
> > > >>> > Now when i type jam on MSYS console, it asks me to set the
> > JAM_TOOLSET
> > > >>> >
> > > >>> >
> > > >>> > Although i did
> > > >>> > set JAM_TOOLSET=MINGW
> > > >>> > still am getting the same message - indicate the toolset.
> > > >>> >
> > > >>> > My OS is WinXP and there i have set jam_toolset=MINGW
> > > >>> >
> > > >>> > The same setting works from the windows command prompt.
> > > >>> >
> > > >>> > What settings do I need to check for jam to work with
> MSYS-MINGW?
> > > >>> > Any help would be appreciated!
> > > >>> >
> > > >>> > Thanks,
> > > >>> > Pranay
> > > >>>
> > > >>>
> > > >>>
> > > >>> _______________________________________________
> > > >>> jamming mailing list  -  jamming at perforce.com
> > > >>> http://maillist.perforce.com/mailman/listinfo/jamming
> > > >>>
> > > >>>
> > > >>>
> > > >>
> > >
> > >
> > >
> >
> >
> > _______________________________________________
> > jamming mailing list  -  jamming at perforce.com
> > http://maillist.perforce.com/mailman/listinfo/jamming
> >
> >
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://maillist.perforce.com/pipermail/jamming/attachments/20070710/6fb84b04/attachment.html


More information about the jamming mailing list