On Mon, 2009-07-20 at 11:01 +0200, Mirco Babin wrote:
>  
> I don't know how these sources should be downloaded. I'm not familiair
> with SVN. Is it possible to provide the sources in a tar or gzip
> or something like that ?

I could, but I'd be re-creating the tarball all the time. It'd be a pain
for both of us.

Subversion is _really_ easy to use. It's a revision control system
vaguely akin to MS SourceSafe, Perforce, etc, though it's much more like
a saner and nicer version of CVS. With it, you can retrieve updates to
the sources quickly and easily, "diff" the sources to see what you've
changed compared to the main version, create patches to send to us to
apply to the main version, etc.

On Windows, install TortoisSVN from http://tortoisesvn.tigris.org/ to
get built-in Subversion support in Windows Explorer.

You can then check the sources out using TortoiseSVN. The URL you want
to check out is:

  https://podofo.svn.sourceforge.net/svnroot/podofo/podofo/trunk

which will get you the latest version of PoDoFo's development tree. You
can then update it to get new changes, etc, easily from within Windows
Explorer.

More information here:

  http://podofo.sourceforge.net/download.html

If you prefer not to install something that affects Windows Explorer, an
alternative is RapidSVN (http://rapidsvn.tigris.org) but I _really_
_strongly_ recommand TortoiseSVN.

Since you'll be using some kind of versioning and revision management
for your main project, you should find svn trivial to use especially
when you're just pulling the PoDoFo sources and updating them.

If you really want you can use the command line client for svn
(http://www.collab.net/downloads/subversion/) from cmd.exe . Just:

cd C:\MyDevelopmentFolder

then all on one line:

svn co 
  https://podofo.svn.sourceforge.net/svnroot/podofo/podofo/trunk
  podofo-trunk

> I have attached CMakeCache.txt to this message.

Great, thanks.

>         >      Comment out in the MD5 part: //#include <sys/types.h>
>         
>         
>         I presume you mean that Borland doesn't have sys/types.h ?
>         
>         If you leave the MD5 part enabled but comment out the include
>         of
>         sys/types.h, what breaks? Can you provide error messages? Is
>         there an
>         appropriate alternative header you can use (which we can add
>         to
>         PdfCompilerCompat.h) ?
>  
> Boland does have sys/types.h

Then what's the problem with the MD5 code? Why do you comment it out?
What errors do you get? Why?
 
>         > 9.09) Edit PdfField.cpp
>         >       void PdfCheckBox::SetChecked( bool bChecked )
>         >       {
>         >           m_pObject->GetDictionary().AddKey( PdfName("V"),
>         (bChecked ?
>         > PdfName("Yes") : PdfName("Off")) );
>         >           m_pObject->GetDictionary().AddKey( PdfName("AS"),
>         > (bChecked ? PdfName("Yes") : PdfName("Off")) );
>         >       }
>         
>         
>         What've you changed? Why?
>  
> I added additional ( ) around "bChecked ? PdfName("Yes"):
> PdfName("Off")". 
> Otherwise Borland won't recognize the '?' ':' construction.

Ah, thanks. Change applied.

>         
>         >       Replace "__FUNCTION__" with "__FUNC__"
>         
>         Compat wrapper PODOFO__FUNCTION__ added. Please add your own
>         clause to
>         PdfCompilerCompat that checks for the Borland compiler.
>  
> Ok

I've done some more research and found a likely candidate predefined
macro. Please test and make sure it's right.

I've used __BORLANDC__ . Sound right? OR should I use __TURBOC__ ?

> My message wasn't meant as a hack, it was meant to provide information
> about Borland compilation and at what points it did fail. I wasn't
> aware that I was suppose to provide suggestions for a solution.

Well, you don't have to. If you do, though, your changes can be applied
to the main version of PoDoFo. That way, when you update you don't have
to go through and do all the changes again, so it makes your life a lot
easier in the long run.

> Next time I will try to provide a solution. You now have introduced
> the PdfCompilerCompat.h. If can get the new sources, I can try to
> compile again

Great, thanks.

By thr way, I didn't mean to sound grumpy - so sorry if I came off that
way. Dealing with compatibility issues with ancient compilers just isn't
my idea of fun, and I prefer the process to be as smooth as possible.
I'd say "so I have time to work on real improvements" but right now, I
rarely do.

-- 
Craig Ringer


------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge  
This is your chance to win up to $100,000 in prizes! For a limited time, 
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize  
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Podofo-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/podofo-users

Reply via email to