On 1 apr. 2013, at 18:33, Ramsey Gurley rgur...@smarthealth.com wrote:
And evidently, I didn't configure my push to push the new 6.0.3 tag :P
Anyway, try the latest master Freddie and see if your problem goes away.
Yes, that resolves the problem!
thanks!!
On Mar 30, 2013, at 11:18
Hi Johnny,
If you need a fix in a hurry and you don't get this one solved, then
ImageMagick can be a reliable alternative for ERAttachment that is also cross
platform too.
MacPorts is the simplest way to install IMHO:
http://www.imagemagick.org/script/binary-releases.php#macosx
$
If you don't want to pollute your system with macports/fink, then you can use
the cactuslabs build: http://cactuslab.com/imagemagick/
/Þór
On 2.4.2013, at 12:55, Kieran Kelleher wrote:
Hi Johnny,
If you need a fix in a hurry and you don't get this one solved, then
ImageMagick can be a
There .. fixed it for you ;)
On Apr 2, 2013, at 9:32 AM, Þór Sigurðsson th...@us.is wrote:
If you don't want to enhance your system with macports/fink, then you can
use the cactuslabs build: http://cactuslab.com/imagemagick/
/Þór
___
Do not
Hi
I am just starting my first ERRest app and playing with ERXKeyFilters.
I have an OrganisationController using a filter and I remove unwanted
attributes from the rest response with:
ERXKeyFilter filter = ERXKeyFilter.filterWithAttributes();
Actually no - since macports and fink install dependant libraries that the
system already has installed, it's hardly an enhancement since now you have
_two_ or more sets of the same libraries which each needs its own method of
updating.
The net result of overusing fink/macports is a machine
You shouldn't hard-code your key values. It should look more like this:
ERXKeyFilter filter = ERXKeyFilter.filterWithAttributes();
filter.exclude(MyEntity.MY_ATTRIBUTE);
filter.exclude(MyEntity.MY_OTHER_ATTRIBUTE);
return filter;
If you want to include a to-one relationship, but none of its
I'm not quite as passionate about it, but that's why I use homebrew. :-)
Tim
UCLA GSEIS
On Apr 2, 2013, at 7:55 AM, Þór Sigurðsson th...@us.is wrote:
Actually no - since macports and fink install dependant libraries that the
system already has installed, it's hardly an enhancement since
If my understanding is correct, Homebrew uses the installed system libraries
whenever possible. That's the reason to use, and to avoid, Homebrew. Install an
app with Homebrew, then update the system from Lion to Mountain Lion and pray
things still work.
With macports, you install a full set of
That could be so I suppose. And, it may be due to the particular packages I
use, but I have never had anything break with the software packages I install.
My experiences with homebrew have been good.
Tim
On Apr 2, 2013, at 9:58 AM, Ramsey Gurley rgur...@smarthealth.com wrote:
If my
Frankly, my most recent experience with all three sucked. I tried installing
octave. fink, macports, and homebrew all failed. I finally found a compiled
package installer for Mac OS X which sorta works. I can't see myself getting to
excited about any of them.
Ramsey
On Apr 2, 2013, at 10:46
Thanks for the advice guys. Although, I'd really like to get the native
going...
The error I'm seeing is a com.webobjects.foundation.NSForwardException
[java.lang.NoClassDefFoundError] Could not initialize class
er.attachment.thumbnail.ImageIOImageProcessor:java.lang.NoClassDefFoundError:
I
OK. So I added this argument to the application's additional arguments in
WOMonitor:
-Djava.library.path=/Library/Java/Extensions:/System/Library/Java/Extensions:/usr/lib/java
And it is now finding the JNI. But now I'm on to a new problem!
java.lang.UnsatisfiedLinkError:
I've had this issue before. There used to be a WO based app for changing your
Open Directory password. It was set up with a JNI library for interfacing with
Apple's directory services frameworks. It no longer ran on 64-bit Intel.
I never tried to dive into XCode and recompile it - so not sure
Hi Tim,
Yeah, I'm getting stumped. I've tried setting x86_64 in the build setting for
all targets and I've even tried compiling with xcodebuild ARCHS=x86_64 from
the command line but no matter what if I run
file libImageIOImageProcessor.jnilib
I get
libImageIOImageProcessor.jnilib: Mach-O
So...
I kind of assumed that since Java 1.6 64 bit was installed that my system was
64 bit. But after running uname -m I see that it is i386. Which is probably
why xcode can't compile the binary to x86_64.
Anybody know why Apple updated Java to 64 bit on a 32 bit machine? And/or how
to
16 matches
Mail list logo
