> serially folks if I am having this much trouble getting this to work it > should be telling us something. Well, your PKG_CONFIG_PATH makes little sense to me, so it's hard to believe that it's a default setting. I don't know where it comes from, but it's easy enough to reset it to a useful value. But first let's try to locate your libxml2.dylib and libxml-2.0.pc. > I got my livxml-2.0 from here > http://www.explain.com.au/oss/libxml2xslt.html[1] This also doesn't seem very kosher. AFAIK recent versions of Mac include libxml2 so why install it again? Is it not included anymore in Lion and Mountain Lion? Also, I bet pkg-config doesn't look in /Library/Frameworks by default. > pkg-config came from MacPorts > > I really think we need to get to a point where we don’t need > pkg-config to get this thing to compile on a Mac, we should be able to > break a new mac out of the boo install Xcode and the CLI tools for > Xcode and have it work. Good point, theoretically it should be possible to do it without pkg-config. We have to figured that out. > On May 13, 2014, at 10:39 AM, Bert Frees <bertfrees@xxxxxxxxx> wrote: > >> >> That path makes no sense at all. Is there something in your ~/.bashrc, >> ~/.bash_profile, ~/.profile, /etc/bash.bashrc or /etc/profile? >> >> Greg Kearney writes: >> >>> Here is what it is set to: >>> >>> gkearney:liblouisutdml-2.5.0 gkearney$ echo $PKG_CONFIG_PATH >>> /usr/local/bin: >>> >>> Where should one find the script that set it? >>> >>> >>> On May 13, 2014, at 10:15 AM, John J. Boyer <john.boyer@xxxxxxxxxxxxxxxxx> >>> wrote: >>> >>>> Greg, >>>> >>>> The only thing lacking is to set the PKG_config_path environment >>>> variable. I'm not sure what its value should be on your version of Mac >>>> OSX, so I won't cause you more frustration by giving a possible setting. >>>> There should be a script that sets it. This would be run before the >>>> configure command. >>>> >>>> John >>>> >>>> On Tue, May 13, 2014 at 09:02:27AM -0700, Greg Kearney wrote: >>>>> OK here is the problem and it always shows up in building liblouisutdml, >>>>> libelous itself build find on a stock Mac. >>>>> >>>>> First I configure, make, make install liblouis everything is fine and the >>>>> various tools work as expected, even the python binding work. >>>>> >>>>> Next I go to build liblouisutdml. I run configure and it dies with the >>>>> following: >>>>> >>>>> checking pkg-config is at least version 0.9.0... yes >>>>> checking for BASE_DEPENDENCIES... configure: error: Package requirements >>>>> (liblouis, libxml-2.0) were not met: >>>>> >>>>> No package 'libxml-2.0' found >>>>> >>>>> Consider adjusting the PKG_CONFIG_PATH environment variable if you >>>>> installed software in a non-standard prefix. >>>>> >>>>> Alternatively, you may set the environment variables >>>>> BASE_DEPENDENCIES_CFLAGS >>>>> and BASE_DEPENDENCIES_LIBS to avoid the need to call pkg-config. >>>>> See the pkg-config man page for more details. >>>>> >>>>> As you can see I have pkg-config installed, I should have the liblouis >>>>> installed as well as I just built and installed it and it tested OK. >>>>> Further I have the libxml-2.0 installed in /Library/Frameworks and they >>>>> test OK as well. So my question is what do I do to get liblouisutdml to >>>>> install and build. >>>>> >>>>> By the way I have an installer that will install and test the libxml-2.0 >>>>> frameworks. >>>>> >>>>> On May 13, 2014, at 8:48 AM, Bert Frees <bertfrees@xxxxxxxxx> wrote: >>>>> >>>>>> >>>>>> Okay so how do we proceed? TBH I still think it shouldn't be that hard >>>>>> for a Perl or Python programmer to get it working. If it is then there's >>>>>> something missing in the documentation. How about we try to get it >>>>>> working for you, then update the documentation, and then see if maybe we >>>>>> need to update your Mac interface? I have relatively recent precompiled >>>>>> versions of liblouis and liblouisutdml that I use in DAISY Pipeline, >>>>>> maybe you can use those for now? As I mentioned before on the mailing >>>>>> list our ultimate goal is to automatically generate nightly builds of >>>>>> the latest versions and make them available for download. >>>>>> >>>>>> Bert >>>>>> >>>>>> >>>>>> >>>>>> Greg Kearney writes: >>>>>> >>>>>>> I could of course make my installer install the programs and files in >>>>>>> any location. I was simply following the paths used by make install. >>>>>>> There could even be a choice. >>>>>>> >>>>>>> There could be any number of reasons why we should want to install the >>>>>>> program but not want to go through the process of compiling it. Despite >>>>>>> what you say on a Mac it is not a simple matter of configure, make, >>>>>>> make install particually I am an experienced user, but not a formal >>>>>>> programmer and I run into issues all the time. >>>>>>> >>>>>>> For example a user might be writing a web interface that needs to call >>>>>>> the various binaries to do translations, a programmer working in Perl >>>>>>> or Python but not familiar with compiling programs might need the >>>>>>> binaries. Perhaps someone would just prefer to use the command line. As >>>>>>> John can tell you I designed a formal MacOS interface for libelous, I >>>>>>> would like to update this by using the more modern tools but I keep >>>>>>> running into the build issues that prevent me from doing so. This is >>>>>>> particularly the case with liblouisutdml which despite having all the >>>>>>> auto-config paths set up still will not build on a standard Mac as >>>>>>> shipped by Apple with the developer tools. >>>>>>> >>>>>>> While a table development tools would be nice I agree I can not wait >>>>>>> about while one gets built. >>>>>>> >>>>>>> >>>>>>> On May 13, 2014, at 6:07 AM, Bert Frees <bertfrees@xxxxxxxxx> wrote: >>>>>>> >>>>>>>> >>>>>>>> Hi Greg, >>>>>>>> >>>>>>>> First of all, we really appreciate your efforts for making liblouis >>>>>>>> more >>>>>>>> easily obtainable for non-developers, and I'm sorry you have to keep >>>>>>>> repeating yourself to get your point across. >>>>>>>> >>>>>>>> Let me start off by reminding that liblouis and liblouisutdml were >>>>>>>> developed as libraries intended to be used in other software with a >>>>>>>> proper user interface, so called frontends, such as BrailleBlaster, >>>>>>>> DAISY Pipeline, NVDA, etc. (correct me if I'm wrong, John). But indeed, >>>>>>>> I agree that there are certain use cases for which the existing >>>>>>>> frontends are not suitable. One of those use cases is table >>>>>>>> developers. However I have different ideas about how to solve that >>>>>>>> problem. >>>>>>>> >>>>>>>> First, I'm not convinced that table developers wouldn't be able to >>>>>>>> build >>>>>>>> liblouis from source. If they can use the liblouis tools to test the >>>>>>>> tables, they are expected to at least have a notion of what the command >>>>>>>> line is, so it can't be that hard to teach them configure && make && >>>>>>>> make install, right? (assuming of course that they are on Linux or >>>>>>>> Mac.) >>>>>>>> >>>>>>>> As David said, it is mostly a matter of documenting things better. If >>>>>>>> you have the right tools, building liblouis from source really isn't >>>>>>>> hard at all. (In your particular case, the error message already gives >>>>>>>> you a big hint. So let's sit together, maybe meet us on the IRC >>>>>>>> channel, >>>>>>>> so that we can guide you through the process.) >>>>>>>> >>>>>>>> Second, I've never been really fond of your idea about making an >>>>>>>> installer that simply puts the binaries into /usr/local/. It just >>>>>>>> doesn't seem right. There is a reason why package managers for Mac OS >>>>>>>> such as fink and homebrew install the binaries in places that they have >>>>>>>> total control of. I would be much happier with for example an >>>>>>>> application bundle that would include all the necessary binaries, >>>>>>>> somewhere under /Applications/Louis.app/Contents/MacOS. >>>>>>>> >>>>>>>> Or would there perhaps be interest in a new frontend dedicated for >>>>>>>> table >>>>>>>> developers? I would include the library and could provide a simple >>>>>>>> interface for testing a table with the need to use the command line. >>>>>>>> >>>>>>>> >>>>>>>> Regards, >>>>>>>> Bert >>>>>>>> For a description of the software, to download it and links to project pages go to http://www.abilitiessoft.com