Ok I could try that.  I'm producing the dist and build folders with many
files in dust not just a single executable.  I do this because I read
somewhere the application runs faster.  It would be nice to have a single
outputs directory somewhere besides where pyinstaller automatically puts
the outputs.  This seems simple and I figured I was just missing
something.   I guess I will just use your batch scripting approach.

On Fri, Apr 3, 2020, 12:34 PM abhishek bhatta <[email protected]>
wrote:

> I usually prefer making a batch/shell script to copy the file after
> creating the executable.
>
> On Friday, April 3, 2020 at 12:49:27 PM UTC+5:30, Rob V wrote:
>>
>> Hello,
>>
>> How do I specify an output directory for the dist and build folders?  I'd
>> like to have one output directory containing results at a user specified
>> location.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "PyInstaller" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pyinstaller/ffbc0cdf-2c9f-4190-a913-04b441ddfc89%40googlegroups.com
> <https://groups.google.com/d/msgid/pyinstaller/ffbc0cdf-2c9f-4190-a913-04b441ddfc89%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
You received this message because you are subscribed to the Google Groups 
"PyInstaller" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/pyinstaller/CAOik8ASW3PJ8E7o585hn3yDpo%2BSgkSADagLurM%2BQCpY%3DFLSpgw%40mail.gmail.com.

Reply via email to