[liblouis-liblouisxml] Re: New At This

  • From: Bert Frees <bertfrees@xxxxxxxxx>
  • To: liblouis-liblouisxml@xxxxxxxxxxxxx
  • Date: Mon, 19 Aug 2013 19:52:52 +0200

If you want to contain the tables in your plugin, either you always have to 
specify the full path to the tables when you invoke liblouis, or you can set 
the LOUIS_TABLEPATH environment variable.


On 19 Aug 2013, at 19:16, John J. Boyer wrote:

> I think Keith is right. If you just unpack the tarball and then use 
> configure, make, make install it should compile with no problems. The 
> dylib will be in /usr/local/lib and the tables will be in 
> /usr/local/share/liblouis/tables I'm not sure what the path to the 
> tables might be in a static library, but you will probably need to  
> emulate the directory structure in share .
> 
> John
> 
> On Mon, Aug 19, 2013 at 04:43:55PM +0000, Keith Creasy wrote:
>> I do not work under OSX or COCOa but as for the constants you can probably 
>> just wrap the liblouis part in a file that does not include the COCOA 
>> headers and likewise not include the liblouis headers in your COCOA code. 
>> That should fix the conflicts.
>> 
>> 
>> I'm sorry I can't be of more help than that.
>> 
>> 
>> -----Original Message-----
>> From: liblouis-liblouisxml-bounce@xxxxxxxxxxxxx 
>> [mailto:liblouis-liblouisxml-bounce@xxxxxxxxxxxxx] On Behalf Of David Lalonde
>> Sent: Monday, August 19, 2013 12:33 PM
>> To: liblouis-liblouisxml@xxxxxxxxxxxxx
>> Subject: [liblouis-liblouisxml] New At This
>> 
>> Hello,
>> 
>> I am new at using liblouis and Apple's XCode and I need help.
>> 
>> I am looking at making a plug-in for use in a software called FileMaker Pro 
>> on Mac OS X that will use the liblouis library. These are the requirements: 
>> the plug-in needs to be self-contained; the translation tables must be 
>> contained in the plug-in.
>> 
>> Before starting off on this endeavour, I attempted to compile the liblouis 
>> code to familiarize myself with the code. I originally followed the 
>> instructions to make a static library. The library could not be used in a 
>> XCode project. I then attempted to compile the code in XCode. Two seemingly 
>> important errors came up: the path to the tables could not be resolved; some 
>> of the constants conflict with Cocoa constants (bold, italic, .).
>> 
>> Can anyone help me by either giving me development advice or generously 
>> offering me a self-contained static library that functions in XCode?
>> 
>> David Lalonde, CC
>> Business and database consultant / Consultant en affaire et en informatique 
>> FileMaker Certified Developer / Développeur certifié FileMaker D-Cogit
>> (519) 631-4646
>> (855) 631-4646 toll-free / sans frais
>> www.d-cogit.caFor a description of the software, to download it and links to 
>> project pages go to http://www.abilitiessoft.com
>> For a description of the software, to download it and links to
>> project pages go to http://www.abilitiessoft.com
> 
> -- 
> John J. Boyer; President, Chief Software Developer
> Abilitiessoft, Inc.
> http://www.abilitiessoft.com
> Madison, Wisconsin USA
> Developing software for people with disabilities
> 
> For a description of the software, to download it and links to
> project pages go to http://www.abilitiessoft.com

For a description of the software, to download it and links to
project pages go to http://www.abilitiessoft.com

Other related posts: