On Tue, Jul 8, 2008 at 2:06 PM, Luc Le Blanc <[EMAIL PROTECTED]> wrote: > My first app segment contains a single C file that embeds all procs > that must be in the first segment in order to be able to properly handle > Global Find and beamed data when the app is not running (i.e. > global-less mode). Now, if I try to link the Glue Library to this in > order to have access to LstGlueSetIncrementalSearch, I get out-of-reach > references to this API. Can I link that single API "in the middle" of my C > file? Otherwise, I tried splitting my C file in two and link the Glue Library > between the two, but that causes lots of 16-bit jump problems. > > Ideas welcome,
why not create a very simple program that calls the LstGlueSetIncrementalSearch function; then you can diassemble it using a combination of par, and pilotdis (par e code 1; pilotdis code0001.bin) then, you'll get a file called code0001.bin.s - which, has the assembly of the small demo program you wrote (that only calls the glue). the glue function will be appended at the end; and you should be able to cut and paste the assembler code into a C function declaration, embedded within "asm" tags. :) thats what i would do. its also a reason why the glue library code should be open source; so one could just use the function that they need (ie: c+p the code where they need) -- // Aaron Ardiri -- For information on using the ACCESS Developer Forums, or to unsubscribe, please see http://www.access-company.com/developers/forums/
