[haiku-3rdparty-dev] Re: Using Paladin (was Porting old BeOS code to Haiku-OS)
- From: "Earl Pottinger" <dmarc-noreply@xxxxxxxxxxxxx> (Redacted sender "earl_colby_pottinger@xxxxxxxxx" for DMARC)
- To: haiku-3rdparty-dev@xxxxxxxxxxxxx
- Date: Fri, 11 Jul 2014 09:48:39 -0700
Thank you for your suggestion. I tried it and Paladin still will not compile
my code.
However, it did seem to go further and now gives me error that are more similar
to the errors I use to get before moving to PM-Haiku.
So thank you for your help.
I am now working documenting the history of development and the past errors I
saw. I hope to post by the weekend.
I am hopeful that someone can then see what I am doing wrong.
Now back to work.
>On Thu, 7/10/14, William Kocay <wkocay@xxxxxxxxxxxxxxxx> wrote:
>Subject: [haiku-3rdparty-dev] Re: Using Paladin (was Porting old BeOS code to
>Haiku-OS)
>To: haiku-3rdparty-dev@xxxxxxxxxxxxx
>Received: Thursday, July 10, 2014, 7:25 AM
>Hello,
>Paladin doesn't like files that end with .c I had this problem when I
>started with Paladin.
>Change it to .cpp and it will likely work.
> --Will
> >Hello,
> >I got onto GitHub and uploaded my code to
> > https://github.com/earl-colby-
> >pottinger/CRAM all the needed files and
> >directories were published.
> >I am testing with Haiku Nightly 47470, if
> >you use the Terminal/CLI and
> >go to the directory CRAM_0.10 and
> >execute the install.sh the driver will
> >compile without error and will
> >install to the right directories with no
> >problems.
> >However, I can not seem to get Paladin to
> >compile without getting lots of errors.
> >I am hoping someone can look at my setup
> >and tell me what I need to do to get
> >Paladin to work.
> >Please,and thank you.
Other related posts:
