NDK 3.1 Include file problem.

[Thorham]

Hi,

After obtaining the NDK 3.1 include files, I've been unable to use any _LVOxxx names in my source code, such as _LVOOpenLibrary and _LVOOpenScreenTagList. In the case of the exec functions in exec_lib.i, the problem seems to be that all functions need this FUNCDEF thing, and for other libraries there's no libname_lib.i at all!

What is going on here? I want to use the NDK 3.1 include files because I only have the Devpak Os 2.x includes, and want to use proper OS 3.0+ include files.

Any help is appreciated

[PeterK]

Hi Thorham,

please, try to include my "ALL IN ONE" LVOs.i instead of lots of these lib_xyz_lvo.i files. I hope it works for you

Tell me if you still need LVOs for other libraries ?!! (Btw, I've renamed some of these 'private' functions)

[phx]

All the LVOs are in amiga.lib. So you just have to import the symbols you need and link your objects with amiga.lib, when generating the executable.

To make it easier you could use Macros like this:

        macro   CALLSYS
        xref    _LVO\1
        jsr     _LVO\1(a6)
        endm

And then just write

        CALLSYS OpenScreenTagList

[Thorham]

Thanks guys

Originally Posted by PeterK

please, try to include my "ALL IN ONE" LVOs.i instead of lots of these lib_xyz_lvo.i files. I hope it works for you

Thanks, but I like to use the standard include files.

Originally Posted by phx

All the LVOs are in amiga.lib. So you just have to import the symbols you need and link your objects with amiga.lib, when generating the executable.

Thanks for explaining, but what the hell did they have to go and do that for? That sucks

Perhaps I'll just stick to the 2.x include files instead. Shouldn't matter much for OS 3.0, right?

[Thorham]

Someone on AmigaOrg told me to just generate the LVOs from the C includes. Guess I'll do that instead Problem solved