OK after many, many steps, I built x01c.c for x86_64 windows from an
ubuntu x86_64 box. pngcairo works fine. Mono and color ps crashes
though. Also I never was able to disable pkg-config, which may or may
not be why during the build process I had to obtain the import libs for
things like freety
Thomas Stover wrote:
> Andrew Ross wrote:
>> Agh! I think the problem might be that the .rc files are blank.
>> Just as a test could you try addding the following to cairo.rc
>> (include only the lines referring to the drivers you have)
>>
>> xcairo:Cairo X Windows Driver:1:cairo:59:xcairo
>> pdfca
Andrew Ross wrote:
> Agh! I think the problem might be that the .rc files are blank.
> Just as a test could you try addding the following to cairo.rc
> (include only the lines referring to the drivers you have)
>
> xcairo:Cairo X Windows Driver:1:cairo:59:xcairo
> pdfcairo:Cairo PDF Driver:0:cairo:
On 2009-03-04 19:37- Andrew Ross wrote:
> On Wed, Mar 04, 2009 at 09:18:36AM -0800, Alan Irwin wrote:
>> On 2009-03-04 10:58- Andrew Ross wrote:
>>
>>> Thinking about it, get-drv-info is only extracting symbols for the installed
>>> drivers which are in the source code anyway. There is no
On Wed, Mar 04, 2009 at 09:18:36AM -0800, Alan Irwin wrote:
> On 2009-03-04 10:58- Andrew Ross wrote:
>
>> Thinking about it, get-drv-info is only extracting symbols for the installed
>> drivers which are in the source code anyway. There is no reason we couldn't
>> have some alternative way of
On Wed, Mar 04, 2009 at 01:12:03PM -0600, Thomas Stover wrote:
>
> >>
> >> -Anyway, example1 runs on my windows machine with this errorish
> >> condition:
> >> *** PLPLOT ERROR, ABORTING OPERATION ***
> >> plInitDispatchTable: Could not open drivers directory, aborting
> >> operation
> >> PLplot
>>
>> -Anyway, example1 runs on my windows machine with this errorish
>> condition:
>> *** PLPLOT ERROR, ABORTING OPERATION ***
>> plInitDispatchTable: Could not open drivers directory, aborting
>> operation
>> PLplot library version: 5.9.2
>> got here -- 0
>
> You are using the dynamic drivers
On 2009-03-04 10:58- Andrew Ross wrote:
> Thinking about it, get-drv-info is only extracting symbols for the installed
> drivers which are in the source code anyway. There is no reason we couldn't
> have some alternative way of doing this using cmake or some scripting which
> would not rely on
On Tue, Mar 03, 2009 at 03:44:45PM -0800, Alan Irwin wrote:
> On 2009-03-03 12:49- Andrew Ross wrote:
>
> > On Mon, Mar 02, 2009 at 11:16:37AM -0800, Alan Irwin wrote:
> >> [...]In sum, my advice [to Thomas was] to stick with CMake (since we
> >> should be able to give
> >> you some help in t
On Tue, Mar 03, 2009 at 03:44:45PM -0800, Alan Irwin wrote:
> On 2009-03-03 12:49- Andrew Ross wrote:
>
>> On Mon, Mar 02, 2009 at 11:16:37AM -0800, Alan Irwin wrote:
>>> [...]In sum, my advice [to Thomas was] to stick with CMake (since we should
>>> be able to give
>>> you some help in that c
10 matches
Mail list logo