Login
Username:

Password:

Remember me



Lost Password?

Register now!

Sections

Who's Online
90 user(s) are online (50 user(s) are browsing Forums)

Members: 0
Guests: 90

more...

Headlines

 
  Register To Post  

SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
Hi All,

I manage to have Code Bench 0.8 setup correct to use SDK 53.xx but now, I encounter another problem,

If I create a new project and use an example, I get error messages.

For example, the BITMAP sample available in REACTION folder does give 45 errors ...
Most of them are related to undefined reference . I have updated the include folder to fit the correct path in SDK ... without success ..

I also often encounter error with :
#Include <MyFile.h>
Saying that # is not correct and < > too...

Does anyone know why ?

All we have to decide is what to do with the time that is given to us.
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@freddix

"#include" (lower case "i").

cheers
tony
Go to top
Re: SDK 53.xx and Code Bench
Supreme Council
Supreme Council


See User information
@freddix

I'm not sure if the reaction examples were verified to compile with this SDK release, so it's possible that errors may creep in.

And as tonyw said, all c preprocessor directives are lower case.

Simon

Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@Rigo
They are all lower case and compilation error occurs ...

For example, the bitmap sample gives :

5 errors :
BitMapExample.c:(.text+0x6?): undefined reference to 'IIntuition'
4 errors :
BitMapExample.c:(.text+0xb?): undefied reference to 'IBitMap'
5 more errors on IIntuition
4 on IWindow
4 more on IIntuition
4 on ILayout
5 more on IIntuition
4 more on IBitMap
and 5 more on IIntuition...

All we have to decide is what to do with the time that is given to us.
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@freddix

seems like a -lauto missing in the makefile. BTW you can first try to compile this sample from the shell
(Make all) and see if it compiles like that, if yes then the problem is in Codebench, if no then the sample's author is to blame...

Back to a quiet home... At last
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@abalaban
How can I compile from shell ?

All we have to decide is what to do with the time that is given to us.
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@freddix

You never programmed in C before, did you ?
The answer was in my previous post :
- you CD into the drawer where the sample is,
- there should be a file named Makefile in it,
- in this case, you can just type "Make all" in your shell

If you never did C programming before I would suggest you to read a C ANSI book before just to understand the basic concepts of C. As C source code can be very difficult to read for novice coming from Basic or derivative languages, for example

vars[*adr++]+=2


This is just to show some valid C/C++ construct, not a sample of readable code...

Back to a quiet home... At last
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@abalaban
I get exactly the same errors when compiling directly from SHELL.

All we have to decide is what to do with the time that is given to us.
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@freddix

so problems are not due to Codebench...

I'm not near my AmigaOne but I'm almost sure that editing the Makefile and adding '-lraauto' and '-lauto' on the link command line could solve your problems...
The link stage is recognizable because it's the only one that uses the final executable name together with the GCC command (I simplify, I hope the makefile is simple).
Makefile main part is structured like this :

<target> : <dependency list space separated>
    <
command to execute>


for the link stage it should be :

<target> will be the name of your executable to generate

<dependency list, space separated> will contain some names (one or more) with a .o extension

<command to execute> should be something like
gcc -o myExecutable objectFile1.o objectFile2.o

just add -lraauto and -lauto at the end of this line.

I suggest you to find a tutorial on Make and it's makefiles format too

Back to a quiet home... At last
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@abalaban
Thank you for these informations.

Now that I have added the option you said, the source code compile, create an executable and it work :)
even under Code BENCH 0.8 :)

Thank you.

All we have to decide is what to do with the time that is given to us.
Go to top
Re: SDK 53.xx and Code Bench
Quite a regular
Quite a regular


See User information
@freddix

Glad I could help you...

Back to a quiet home... At last
Go to top

  Register To Post

 




Currently Active Users Viewing This Thread: 1 ( 0 members and 1 Anonymous Users )




Powered by XOOPS 2.0 © 2001-2023 The XOOPS Project