auto-py-to-exe with unusual directory structure

[krow4869]

So I have a fairly large python project with 262 files across 25 folders. The program starts at C:/somepath/main/main/main.py. Given that I have two directories and a file of the same name, and some assets and other python files outside the directory containing main.py, I have no idea on how to use the auto-py-to-exe tool for this. I watched youtube tutorials and read the official README of auto-py-to-exe but the instructions were only for one file/one directory projects, and there was no instructions for this structure.

How should I configure the auto-py-to-exe?

The directory structure looks something like this:

Output:
C:/somepath/main
		/main
			__init__.py
			main.py
			otherfiles.py
			/sub
				__init__.py
				subfile1.py
				othersubfile.py
				...
			/othersub
				__init__.py
				otherrsubfile.py
				...
			...
		/images
			img1.png
			img2.png
			...
		/locales
			/en
				...
			/de
				...
			/fr
				...
			/it
				...
		...

[random_nick]

There is little sense in having multiple folders of the same name. Have you thought of changing your repo structure so it would be more explicit, e.g.,

Output:
your_project_name
	docs
	resources
		images
		locales
	src
		package1
			logic.py
			gui.py
			controller.py
		package2
			logic.py
			gui.py
			controller.py
		controller.py

Anyway, I've never used auto-py-to-exe, but pyinstaller works quite fine for me for multi-level projects. I just type pyinstaller project.py and it picks up almost everything automatically.

[krow4869]

After your suggestion, the new file structure is some thing like this:

Output:
C:/Users/Tedu/Desktop/bkchem
    /src    (main folder, previously named bkchem so only the parent and child of src are named bkchem)
        /oasa
            /oasa
                /graph
                    __init__.py
                    basic.py
                    diedge.py
                    ...
                __init__.py
                atom.py
                bond.py
                ...
            __init__.py
            test.py
            convert.py
            ...
        /plugins
            /piddle
                __init__.py
                ...
            __init__.py
            cairo.py
            piddle.py
            ...
        __init__.py 
        bkchem.py               (the file that executes the script)
        ...                     (other files for gui, databases, etc.)
    /dtd                        (some special data folder)
        cdml.dtd
        cdml.xsd
        ...
    /images                     (directory that stores the splash screen, accepts images from users)
        icon.ico
        logo.gif
        ...
    /locale    (language data)
        bkchem.pot
        /fr
            french.mo
        /de
            german.mo
    /pixmaps                    (icons for buttons)
        arrow.gif
        adder.gif
        ...
    /templates                  (well, templates)
        ...

When I executed the command pyinstaller -w ./Desktop/bkchem/bkchem/bkchem.py, as per your suggestion, I got these in the prompt (I don't know if they're relevant):

Output:
133 INFO: UPX is not available.
137 INFO: Extending PYTHONPATH with paths
['C:\\Users\\Tedu\\Desktop\\bkchem', 'C:\\Users\\Tedu']

and when I ran the created executable, a dialog box said 'Failed to execute script bkchem'. I'm pretty sure the code worked in Python.

[random_nick]

When I executed the command pyinstaller -w ./Desktop/bkchem/bkchem/bkchem.py

I would rather cd to the final location and run pyinstaller in the same folder.

Output:
133 INFO: UPX is not available.
137 INFO: Extending PYTHONPATH with paths
['C:\\Users\\Tedu\\Desktop\\bkchem', 'C:\\Users\\Tedu']

UPX just compresses EXE files, you don't have to worry about it. Is it your full output? When the program is successfully built, the output is much longer.

and when I ran the created executable, a dialog box said 'Failed to execute script bkchem'. I'm pretty sure the code worked in Python.

You're missing some modules. Create a copy of your repo, strip it of large third-party libraries, cut down your imports to the minimum and try again.

I should say, building to EXE is not a simple process (at first) and WILL give much headache to those who have never dealt with it. Try building a hello world first, than add GUI, then one-by-one add extra modules. At that point, you will be sure what causes the error. When adding some module fails, that would mean you have to find missing libraries and copy them to your build manually. I had such problem with tkinterhtml and solved it when manually copied Lib/site-packages/tkinterhtml/tkhtml/Windows to folder_with_your_main_built_bin/tkhtml. These are likely to be pre-built platform-dependent binaries that are not being build with pyinstaller during the building process.