Sdk 53.20 issues

Sdk 53.20 issues

Posted on: 2013/6/3 18:40 #1

Just popping in

I'm trying to reinstall sdk but when i try, it says: openinf of file failed in archive perl-5.8.5.
Any clue?

Re: Sdk 53.20 issues

Posted on: 2013/6/3 19:30 #2

Home away from home

redownload the SDK, probably a faulty archive

People are dying.
Entire ecosystems are collapsing.
We are in the beginning of a mass extinction.
And all you can talk about is money and fairytales of eternal economic growth.
How dare you!
– Greta Thunberg

Re: Sdk 53.20 issues

Posted on: 2013/6/3 23:41 #3

Home away from home

Are you installing over an old SDK or a new install?

Some perl files may well be write protected, so might not like being overwritten.

Otherwise I'd go with the possible corrut archive sugestion above.

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/5 13:09 #4

Just popping in

thk you for your answers!
i downloaded again sdk but there's the same problem.
(I upgraded the old installation)
I disabled perl installation and it worked fine!
Strange thing is when i double click on sdk installer it says something like "folder @#à@à is not empty. would you like to continue?". It seems the name is made by trashed characters. I answer yes and after a little if there's perl it gives me the error message.
How can i disable write protection of a folder and all of its children?

Re: Sdk 53.20 issues

Posted on: 2013/6/5 13:18 #5

Home away from home

There is no "upgrade" for the SDK (you'll get in lots of troubles as you see now)
The most problematic part are the links to already isntalled shared objects (they can't be used twice and will end up in error messages while installing and a not 100% functional SDK)

Believe me, i did it wrong myself

1) Install the SDK to a NEW directory
2) Reboot
3) Delete the old SDK directory
4) Let AmiUpdate find and install all the updates
5) Happy coding

Edit: Don't mess with the SDK afterwards (paths, assigns etc.)...it's in a state now that, if installed correctly, works perfectly fine.

Again, believe me, i did it wrong already

MickJT

Re: Sdk 53.20 issues

Posted on: 2013/6/5 13:34 #6

Quite a regular

If you install the SDK to a new directory, I don't know what that will do to the existing assigns in User-Startup (whether it'll change them, or add new ones and cause a conflict).

Here's what I'd do:

1) Within DOpus4, delete your SDK directory. It will prompt you to unprotect some files to continue deleting.

2) Remove any reference to the SDK from User-Startup. Then reboot.

3) After rebooting, reinstall the SDK. Reboot again.

Chris

Re: Sdk 53.20 issues

Posted on: 2013/6/5 15:09 #7

Amigans Defender

I rename the old SDK dir (any assigns or locks move with the rename)
Then install the new one
Reboot and you can then delete the old dir, or move anything over from it you need (usually "local")

Re: Sdk 53.20 issues

Posted on: 2013/6/5 15:11 #8

Home away from home

@MickJT

What you should do is:

Rename the sdk directory (not delete) eg;

rename Programming:SDK Programing:SDK.old

leave the startup sequence alone

install new SDK

copy anything in SDK:Local/ from the old sdk that you might need, eg. third party libraries / includes etc.

or

resintall those third party libs you need from scratch.

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/5 15:15 #9

Home away from home

Quote:

How can i disable write protection of a folder and all of its children?

protect all Programming:sdk/ +w+d

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/5 15:22 #10

Home away from home

Quote:

MickJT wrote:
If you install the SDK to a new directory, I don't know what that will do to the existing assigns in User-Startup (whether it'll change them, or add new ones and cause a conflict).

As i already tried it pretty often i can tell

When one installs a new SDK it will change the user-startup entries to the new paths (mind you, ONLY if those user-startup entries HAS NOT been changed in the meantime) iirc it looks for
Quote:

;BEGIN AmigaOS 4.1 SDK
...
...
;END AmigaOS 4.1 SDK

and changes the pathes accordingly.

So, after a reboot the new paths gets used and one can savely delete the old SDK dir.

Re: Sdk 53.20 issues

Posted on: 2013/6/5 15:26 #11

Home away from home

Quote:

broadblues wrote:
@MickJT

What you should do is:

Rename the sdk directory (not delete) eg;

rename Programming:SDK Programing:SDK.old

leave the startup sequence alone

install new SDK

copy anything in SDK:Local/ from the old sdk that you might need, eg. third party libraries / includes etc.

or

resintall those third party libs you need from scratch.

Actually i wouldn't do that unless you
a) explicitely know what you are doing or it might break something (AmiUpdate support i.e)
b) have your own library builds in there which can't be downloaded from somewhere else.

For a "normal" user a reinstall and AmiUpdate should be sufficient imho

MickJT

Re: Sdk 53.20 issues

Posted on: 2013/6/7 8:58 #12

Quite a regular

@Raziel

What broadblues said is OK so long as all the pkgconfig (.pc) and <name>-config files are copied along with the header (include) files, and the paths aren't mixed up (if it was in common/include, don't put it newlib/include, and vice versa).

Re: Sdk 53.20 issues

Posted on: 2013/6/7 23:43 #13

Just popping in

Reinstalled 53.20.
Now when i try to compile a mui program shell says:
error proto/muimaster.h no such file or directory...
error libraries/mui.h no such file or directory...
error proto/alib.h no such file...
...
What can i do??

Re: Sdk 53.20 issues

Posted on: 2013/6/7 23:51 #14

Home away from home

@MickJT

Quote:

What broadblues said is OK so long as all the pkgconfig (.pc) and <name>-config files are copied along with the header (include) files, and the paths aren't mixed up (if it was in common/include, don't put it newlib/include, and vice versa).

Well obviously you would copy files keeping the path consistent.

As to pkconfig, I can't remember any project I tried build where that worked. Do we actually have a working port of it?

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/8 0:56 #15

Just popping in

Now it gives me another error (solved the other copying mui includes in include_h):

/SDK/include/include_h/interfaces/muimaster.h ... error: muiprog.h no such file or directory.
????

Re: Sdk 53.20 issues

Posted on: 2013/6/8 13:23 #16

Home away from home

Quote:

Now it gives me another error (solved the other copying mui includes in include_h):

You should probably have added -I/SDK/MUI/C/include to your compile flags if that directory isn't in the compiler include path already.

You certainly should not copy anything into SDK:include/include_h that is for system includes only.

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/8 16:37 #17

Just popping in

Ok!!! Now it gives me Undefined references to IAHI and IMUIMASTER...
I.E. i looked a function where the only written code is "AHI_ControlAudio(....TAG_END);
and here there's a undefined reference to IAHI.
What's IAHI?

Re: Sdk 53.20 issues

Posted on: 2013/6/8 21:50 #18

Home away from home

Quote:

Ok!!! Now it gives me Undefined references to IAHI and IMUIMASTER...
I.E. i looked a function where the only written code is "AHI_ControlAudio(....TAG_END);
and here there's a undefined reference to IAHI.
What's IAHI?

IAHI and IMUIMASTER (correct captilisation?) are the interfaces for ahi.device amd muimaster.library respectively.

Are you porting 3,x code? If so you need to add an GetInterface() call to get the interface from the library bases.

Blender For OS4.x : Blues : Walker Broad

Re: Sdk 53.20 issues

Posted on: 2013/6/9 0:29 #19

Just popping in

@broadblues:
thk you for your patience!
I'm porting a program i wrote in aros. Just a little guitar tuner to learn ahi.
I usually work in aros because i use it on my notebook, then i ported it to morphos and now i'm trying to port it to os4.