Hi Curt,
On Wed, 15 Apr 2009, Curt, WE7U wrote:
I was going to use the Unix Epoch timestamps,
Ok, use `date +%s` instead.
and check that the
file was actually done being written, but yea, that's the idea.
Shouldn't matter. On Linux/FreeBSD/Mac OS X you can rename (or even
delete) the
On Wed, 15 Apr 2009, Gerry Creager wrote:
Personally, I think you ought to use the MD5 of the image as a seed for a
RAND, and use that as the filename. A similar approach could be used for the
extension.
Ahhh, a challenge. Well, a bit of one. grin
while [ 1 ]; do
kill -SIGUSR1
Hi Jason,
On Wed, 15 Apr 2009, Jason KG4WSV wrote:
On Wed, Apr 15, 2009 at 9:04 PM, Carl Makin c...@stagecraft.cx wrote:
Um, the uuid thing only works on linux with /proc enabled.
/dev/urandom usually has some good stuff in it...
Yes, but the output isn't plaintext. /proc/sys/kernel
Afternoon All,
I've just created a FreeBSD port skeleton that will make it easy for
FreeBSD users to track the most current sources in CVS.
The information on how to use it, and where to get it are up on the
Xastir Wiki at;
http://www.xastir.org/wiki/index.php/FreeBSD
(Scroll to the
Hi Bob,
On 19/12/2009, at 2:19 PM, Bob Nielsen wrote:
What's wrong with just using CVS to update to the latest. It works
with OS X, which is sort of FreeBSD-ish.
It does use CVS to download the latest. The port just wraps it all up
making it very easy and integrates it with the packages
Hi Curt,
On 19/12/2009, at 3:22 PM, Curt, WE7U wrote:
Or... Set up the port code to download a specific version from CVS
via a CVS tag, which will make sure the same code is downloaded each
time. Or set it up to download a specific *.tgz file from
SourceForge which guarantees the same thing.
Afternoon All,
FYI the Xastir version in MacPorts has been updated to 1.9.8
Thanks to Ryan, ryandes...@macports.
Carl.
(vk1kcm)
___
Xastir mailing list
Xastir@lists.xastir.org
http://lists.xastir.org/cgi-bin/mailman/listinfo/xastir
Hi Curt,
On 24/06/2010, at 9:13 AM, Curt, WE7U wrote:
The only concern I'd have is: What OS'es are supported by
VirtualBox? Do they support OSX? I know there's already an OSX
VirtualBox has full support and commercial builds on Windows, OSX,
Linux and Solaris X86. There is also an Open
Hi Tom,
On 21/09/2010, at 3:09 PM, T Wegner wrote:
Following the sites instructions, I installed what I could using
MacPorts. The instructions noted that shapelib and geotiff can not
be installed with MacPorts, and provided the instructions I've been
posting in my problem threads. This is
Hi Tom,
No problems with the effort, we're happy to help.
On 22/09/2010, at 12:17 PM, T Wegner wrote:
6) ./configure --with-bdb-incdir=/opt/local/include/db42 --with-
bdb-libdir=/opt/local/lib/db42
./configure --with-bdb-incdir=/opt/local/include/db46/ --with-bdb-
Evening All,
On 05/10/2010, at 1:04 PM, Chase Turner wrote:
After trying to build it all from source, mainly without a good
instruction
set- what most linux/command line nerds seem to enjoy is watching
newbies
such as myself struggle with substandard instructions and then snarky
comments
Evening All,
The FreeBSD port of Xastir is currently broken if you upgrade to the latest
version of ImageMagick in ports. This is due to the ImageMagick port having
HDRI support enabled by default.
I have just submitted an update to the FreeBSD Xastir port skeleton that will
remove the option
Hi Tom,
> On 1 Jul 2019, at 11:22 am, Tom Russo wrote:
>
> Fixed in commit 7b6ecce5.
>
> On Sun, Jun 30, 2019 at 07:03:16PM -0600, we recorded a bogon-computron
> collision of the flavor, containing:
>> I am removing the function call and the kludge that made us include
>> private
> On 14 Jul 2019, at 7:26 pm, Carl Makin wrote:
> Would it be worthwhile pushing this as a point release?
Actually, don’t worry about it. I’ll add the patch manually.
Thanks,
Carl.
(vk1kcm)
___
Xastir mailing list
Xastir@lists.xastir.or
I’ve just submitted the update for the FreeBSD port of Xastir 2.1.4.
This update removes GDAL, any mention of ImageMagick and makes ports Shapelib a
dependency (rather than optional).
It compiles by default using gcc, but if GraphicsMagic is deselected in ‘make
config’ then it will compile
Hi Everyone,
The port was committed last night, and is available via portsnap (or whatever)
now. It will obviously take a little while to become available via pkg.
Thanks to everyone who helped, especially the Xastir team.
Carl.
(vk1kcm)
___
Xastir
Hi Tom, Everyone,
> On 18 Jul 2019, at 2:09 am, Tom Russo wrote:
>
> Really, Carl just needs to work through whether to make the default Xastir
> build use GraphicsMagick as the 2.1.0 port was (which forces Xastir to be
> built with gcc8) or ImageMagick6 (which lets Xastir be built with clang,
Hi Tom,
> On 15 Jul 2019, at 11:27 pm, Tom Russo wrote:
> Is there a reason you had to remove all reference to imagemagick? Xastir
> still builds with either ImageMagick or GraphicsMagick, and we test both.
> There was brief discussion of removing ImageMagick support, but we discarded
> that
Hi Tom,
> On 16 Jul 2019, at 12:14 pm, Tom Russo wrote:
>
> Years ago, ImageMagick was so frequently breaking their API that we went to
> preferring GraphicsMagick -- if configure detects both, it uses
> GraphicsMagick.
> But if only IM is installed, or if both are installed and GM doesn't
> On 17 Oct 2022, at 8:53 am, Larrie Deardurff wrote:
>
> Hi
>
> I am trying to get Xastir to run on my MacBook Air running OS 12 Monterrey.
> I installed it via Macports. Install successful but Xastir starts but does
> not run. Starting from terminal, I get the error that Xastir "can’t
Evening All,
I've just re-implemented an interface to the native Mac speech routines in
Xastir.
It's not the nicest interface since the Core Foundation based API to the Mac
speech functionality gets quite upset and yells at you if you call it after a
fork so I used execl to run /usr/bin/say
Hi,
I've just struck the pkglib is not a legitimate directory for SCRIPTS problem
with automake 1.12.
I've got a patch for it which has the side effect of moving the scripts
directory from /usr/local/lib/xastir/ to /usr/local/share/xastir/scripts/.
I personally prefer the new directory as it's
Evening All,
I have a couple of problems that I'm working through with the FreeBSD builds of
Xastir.
Firstly I'm getting a compile error;
map_geo.c:2127: error: invalid operands to binary
map_geo.c:2128: error: invalid operands to binary
map_geo.c:2129: error: invalid operands to binary
Hi Everyone,
FYI I have submitted an update to the FreeBSD Xastir port to bring it up to
2.1.0.
If you want to play with it before it gets committed you can grab the diff
from;
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226187
Carl.
(vk1kcm)
—
Bug 226187
Summary:
24 matches
Mail list logo
