[chirp_devel] FT70

[Harold Hankins]

On Linux I had to append --log=chirp.log to the command to get it to create
a log.  It created the log in the directory I was in.
I also added an environment variable CHIRP_DEBUG=debug to set the level of
logging but I don't think it was necessary to get a log file.

-Hank

On Sun, Mar 18, 2018 at 6:00 PM, Fred Munden via chirp_devel <
chirp_devel at intrepid.danplanet.com> wrote:

> the directory
>
> C:\Users\{your_user_name}\AppData\Roaming\Chirp is present with stock_configs directory and chirp.config file.
>
> I did not do an install I'm executing from chirp.hg directory.
>
> I started chirp from a administrator cmd window.  python chirpw
>
> this is the first time chirp has been excuted on this notebook (win7)
>
>
>
>
> _______________________________________________
> chirp_devel mailing list
> chirp_devel at intrepid.danplanet.com
> http://intrepid.danplanet.com/mailman/listinfo/chirp_devel
> Developer docs: http://chirp.danplanet.com/projects/chirp/wiki/Developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://intrepid.danplanet.com/pipermail/chirp_devel/attachments/20180318/60d1c290/attachment-0001.html