Re: PRIll?

* Nate Bargmann <n0nb <at> yahoo.com> [2005 Jan 28 14:57 -0600]:
> A few days ago Stephane uploaded a series of patches
> to transition away from lld/lli and inserted PRIfreq
> in its place.  I noticed that the last occurance in
> each file the substitution became PRIll rather than
> PRIfreq.  I have a computer issue that prevents me
> from compiling right now (I removed a noisy fan from
> my northbridge and now the machine locks up on
> compilation).
> 
> I didn't find PRIll defined in rig.h, so before I
> upload a series of untested patches I want to make the
> list aware of this discrepancy.

Joop has let me know that it compiles fine for him.  I guess I need to
fix my machine and do a few tests.

73, de Nate >>

--

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info  <at>   | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR  <at>             |     a GNU generation!"
        http://www.networksplus.net/n0nb/       |   http://www.debian.org

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.

Testing

I installed a new mailer and I think this fixed my problems sending
mail to Source Forge.

73, de Nate >>

--

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info  <at>   | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR  <at>             |     a GNU generation!"
        http://www.networksplus.net/n0nb/       |   http://www.debian.org

-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl

Re: PRIll?

On Thu, Jan 27, 2005 at 03:59:37AM -0800, Nate Bargmann wrote:
> A few days ago Stephane uploaded a series of patches
> to transition away from lld/lli and inserted PRIfreq
> in its place.  I noticed that the last occurance in
> each file the substitution became PRIll rather than
> PRIfreq.  I have a computer issue that prevents me
> from compiling right now (I removed a noisy fan from
> my northbridge and now the machine locks up on
> compilation).
> 
> I didn't find PRIll defined in rig.h, so before I
> upload a series of untested patches I want to make the
> list aware of this discrepancy.

PRIll is defined in src/misc.h, and apply to 64bit ints,
and is only for internal use (not part of exported API).

PRIfreq is defined in rig.h, and pertain to the freq_t type,
which is actually a double float.

Rem: we cannot use the freq typing everywhere because of 
the rounding "feature" of *printf formating.

So basically in frontend/backends, use PRIfreq for debugging
or formating with real precision, and use PRIll (along with 
appropriate type casting) to format a huge integer number.

73,
Stephane - F8CFE

Re: PRIll?

* Stephane Fillod <f8cfe <at> free.fr> [2005 Feb 07 16:46 -0600]:
> PRIll is defined in src/misc.h, and apply to 64bit ints,
> and is only for internal use (not part of exported API).
> 
> PRIfreq is defined in rig.h, and pertain to the freq_t type,
> which is actually a double float.
> 
> Rem: we cannot use the freq typing everywhere because of 
> the rounding "feature" of *printf formating.
> 
> So basically in frontend/backends, use PRIfreq for debugging
> or formating with real precision, and use PRIll (along with 
> appropriate type casting) to format a huge integer number.

Very good.  I was just surprised to see PRIll in the
ft_920_send_dial_freq() function of ft920.c in the rig_debug() call
while all the other functions calling rig_debug use PRIfreq.  In fact,
ft_920_send_dial_freq() has an earlier rig_debug() call that uses
PRIfreq!

I see that you used PRIll to display the result of a from_bcd() call
which is probably a good idea.  Now that I know the difference, I won't
worry about it.

So, anytime a frequency value is passed to/from the frontend, PRIfreq
is prefered and for internal calculations PRIll is probably prefered.

73, de Nate >>

--

-- 

Racal RA37xx

Building under MINGW

I'm sure I'm doing something wrong - using Msys/Mingw under Win2k, 
trying to build the released 1.2.3.

What should the incantations be? I'm not familiar with the Linux/GNU 
style tools, I'm normally using Borland BCB or MSVC - I'm an 
experienced programmer, just not on this platform.

I did (in Msys)

sh ./configure
make

and it built the front end, but fell over on the first back end module.

I'm hoping to integrate rig control into my VHF contest logging 
software (currently being moved from DOS to Win32); and no, changing to 
Linux isn't the answer (yet, anyway - if I can I'll make the program 
cross platform) - most end users have enought trouble with DOS/Windows, 
without trying to persuade them to use Linux!

I'll be testing initially on an FT1000MP, so I may be able to feed back 
some experience from that - if I can build it!

Mike G0GJV

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Building under MINGW

Hello Mike,

On Wed, Feb 16, 2005 at 08:14:11PM +0000, g0gjv wrote:
> I'm sure I'm doing something wrong - using Msys/Mingw under Win2k, 
> trying to build the released 1.2.3.

So far, nothing wrong 

> What should the incantations be? I'm not familiar with the Linux/GNU 
> style tools, I'm normally using Borland BCB or MSVC - I'm an 
> experienced programmer, just not on this platform.

I've never done it with Msys/Mingw, only with Cygwin or Linux/Mingw.
Let's make it to work with Msys/Mingw!

> I did (in Msys)
> 
> sh ./configure
> make
> 
> and it built the front end, but fell over on the first back end module.

Can you please report the error messages (traces) ?
If it's broken, we've got to fix it!

> I'm hoping to integrate rig control into my VHF contest logging 
> software (currently being moved from DOS to Win32); and no, changing to 
> Linux isn't the answer (yet, anyway - if I can I'll make the program 
> cross platform) - most end users have enought trouble with DOS/Windows, 
> without trying to persuade them to use Linux!

Hamlib is not Linux centric. It's running under FreeBSD/NetBSD, Mac OS
X, and Windows!
For your information, there's a binary release for Windows available at
the sourceforge download korner, with suitable import libraries for MSVC
and GCC/Mingw.

Once the rig control integration is done, let us know if there's a web
page talking about your VHF contest logger, so we can add a link to it.

> I'll be testing initially on an FT1000MP, so I may be able to feed back 
> some experience from that - if I can build it!

Your feedback will be welcome, once we have sorted out the build
process.

73's
--

-- 
Stephane - F8CFE, square:IN98EC

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Racal RA37xx

Hi Danny,

On Mon, Feb 14, 2005 at 09:08:31PM -0000, DANIEL HIGGINS wrote:
> I have recently procured an RA3702 with manuals and hopefully some more RA3712s (dual 40MHz version) to
follow.  I will be writing some software to control them, but my first job is to use the serial data output
from the receiver to control a matching drive unit (MA3772) with a programmable offset (+/- 10 kHz) for
transceiver operation, using a PIC.
> 
> Let me know if you need the chapter on remote control (about 58 pages).

Having the remote control manual would sure help. Do you have it in
electronic form? only paper?

Perhaps would you like to volunteer to write the Hamlib backend of that radio?
There's support already for the RA6790 (untested due to lack of hardware),
but I have no idea if protocol is the same as the RA3702 or different.
Anyway, you're welcome in the Hamlib team!

Regards,
--

-- 
Stephane - F8CFE

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Building under MINGW

I'll try again, with the correct "from" address...

In article <20050216221207.GN4452 <at> charybde.local>, Stephane Fillod 
wrote: 
> Can you please report the error messages (traces) ? 
> If it's broken, we've got to fix it! 
> 

tail end of Msys display 

Making all in src 
make[1]: Entering directory `/e/hamlib-1.2.3/src' 
make[1]: Nothing to be done for `all'. 
make[1]: Leaving directory `/e/hamlib-1.2.3/src' 
Making all in icom 
make[1]: Entering directory `/e/hamlib-1.2.3/icom' 
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. 
-I../include -I../include -I../src -I../lib    
-g -O2 -Wall -MT ic706.lo -MD -MP -MF ".deps/ic706.Tpo" \ 
 -c -o ic706.lo `test -f 'ic706.c' || echo './'`ic706.c; \ 
then mv -f ".deps/ic706.Tpo" ".deps/ic706.Plo"; \ 
else rm -f ".deps/ic706.Tpo"; exit 1; \ 
fi 
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib 
-g -O2 -Wall -MT ic706.lo -MD -MP -MF 
.deps/ic706.Tpo -c ic706.c  -DDLL_EXPORT -DPIC -o .libs/ic706.o 
gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib 
-g -O2 -Wall -MT ic706.lo -MD -MP -MF 
.deps/ic706.Tpo -c ic706.c -o ic706.o >/dev/null 2>&1 
make[1]: *** [ic706.lo] Error 1 
make[1]: Leaving directory `/e/hamlib-1.2.3/icom' 
make: *** [all-recursive] Error 1 

> Hamlib is not Linux centric. It's running under FreeBSD/NetBSD, Mac 
OS 
> X, and Windows! 
> For your information, there's a binary release for Windows available 
at 
> the sourceforge download korner, with suitable import libraries for 
MSVC 
> and GCC/Mingw. 
> 

I know - thats why I'm looking at it. I've already been looking at the 
prebuilt binaries, and proved that they 
do talk to my rig - now I'm looking at what I can do from code as well. 

> Once the rig control integration is done, let us know if there's a 
web 
> page talking about your VHF contest logger, so we can add a link to 
it. 
> 

It'll be where the current one is - http://www.goodey.org.uk 

When I've got a bit further with it, if anyone is interested in joining 
in as an open source effort... let me 
know, and we can see where it takes us. I have some fairly firm 
architectural views on how it will work, but I 
want to get some proving work done first. 

Mike G0GJV IO91OK 

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

Re: Building under MINGW

In article <20050216221207.GN4452 <at> charybde.local>, Stephane Fillod wrote:
> Can you please report the error messages (traces) ? 
> If it's broken, we've got to fix it!
>

tail end of Msys display

Making all in src
make[1]: Entering directory `/e/hamlib-1.2.3/src'
make[1]: Nothing to be done for `all'.
make[1]: Leaving directory `/e/hamlib-1.2.3/src'
Making all in icom
make[1]: Entering directory `/e/hamlib-1.2.3/icom'
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src
-I../lib   
 -g -O2 -Wall -MT ic706.lo -MD -MP -MF ".deps/ic706.Tpo" \
  -c -o ic706.lo `test -f 'ic706.c' || echo './'`ic706.c; \
then mv -f ".deps/ic706.Tpo" ".deps/ic706.Plo"; \
else rm -f ".deps/ic706.Tpo"; exit 1; \
fi
 gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -g -O2 -Wall -MT ic706.lo -MD
-MP -MF 
.deps/ic706.Tpo -c ic706.c  -DDLL_EXPORT -DPIC -o .libs/ic706.o
 gcc -DHAVE_CONFIG_H -I. -I. -I../include -I../include -I../src -I../lib -g -O2 -Wall -MT ic706.lo -MD
-MP -MF 
.deps/ic706.Tpo -c ic706.c -o ic706.o >/dev/null 2>&1
make[1]: *** [ic706.lo] Error 1
make[1]: Leaving directory `/e/hamlib-1.2.3/icom'
make: *** [all-recursive] Error 1

> Hamlib is not Linux centric. It's running under FreeBSD/NetBSD, Mac OS 
> X, and Windows! 
> For your information, there's a binary release for Windows available at 
> the sourceforge download korner, with suitable import libraries for MSVC 
> and GCC/Mingw.
>

I know - thats why I'm looking at it. I've already been looking at the prebuilt binaries, and proved that they 
do talk to my rig - now I'm looking at what I can do from code as well.

> Once the rig control integration is done, let us know if there's a web 
> page talking about your VHF contest logger, so we can add a link to it.
>

It'll be where the current one is - http://www.goodey.org.uk

When I've got a bit further with it, if anyone is interested in joining in as an open source effort... let me 
know, and we can see where it takes us. I have some fairly firm architectural views on how it will work, but I 
want to get some proving work done first.

Mike G0GJV IO91OK

-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click