Issues installing Windows binary (CloudComPy310)

[MattGuenther]

Hello, please delete this if this is not the appropriate place to ask this question.

I have downloaded the CloudComPy310 binary for Windows 10 and have attempted to follow the instructions in UseWindowsCondaBinary.md. However, this is my first time ever using Anaconda or doing any coding beyond basic Python and I am having some issues. I can get through all of the set up steps except for the last. Whenever I run "envCloudComPy.bat" in the Anaconda Powershell Prompt console, I get the message: "rem this script sets the environment for CloudComPy. The Conda environment must be activated before calling this script."

I have activated the CloudComPy310 environment that I set up according to the specifications in the document, and used the "cd" command to point to the directory where I downloaded the binary file to (C:\CloudComPy310) before trying to run the .bat. Is there something obvious I am overlooking? I have already tried deleting and re-installing Anaconda and deleting my CloudComPy310 environment and re-creating it. I also went through the results of "conda list" and compared to the building directory "conda-list_Windows10_310" and ensured all packages were in my environment.

I would really appreciate any guidance on this. Thank you.

[prascle]

Hello, It looks like you did everything correctly! The message still appears and is just a reminder to remember to enable the conda environment first, maybe it is confusing. What happens when you try to run CloudCompare or the Python tests after that? Let me know the results. Maybe I should change the message to avoid confusion, or check and show a diagnosis only if there is a problem? Thanks, Paul

[MattGuenther]

Thank you for getting back to me so quickly. I just finished running the Python tests and they worked successfully. I had interpreted the message shown after running the .bat file as indicating that the Conda environment had not been successfully/correctly activated but I also am very new to Conda/working with scripts in general. Thanks again.

[maopi-boom]

Hello, you and I have encountered the same confusion. Have you solved it? thank

[ghost]

Hello, you and I have encountered the same confusion. Have you solved it? thank

Hey, I also have the same issues. Did you solve it?

[MattGuenther]

Sorry for not getting back to you sooner- if you are still having this problem, I was able to get everything working by creating an Anaconda environment 'CloudComPy310" with a path of "D:/Anaconda/envs/CloudComPy310". I also put the decompressed Zip file containing the downloaded CloudComPy310 binary in the same directory as the Anaconda install, " D:/CloudComPy310". Using the Anaconda terminal for the CloudComPy310 environment, run the following commands:

1. conda activate CloudComPy310
2. cd D:/CloudComPy310
3. envCloudComPy.bat
4. Python D:/YourPythonScript.py

Hopefully this works- and if anyone more knowledgeable than me has a simpler, more improved solution, please let me know.

On Wed, Jul 26, 2023 at 6:47 AM ulugbekait @.***> wrote:

Hello, you and I have encountered the same confusion. Have you solved it? thank [image: image] https://user-images.githubusercontent.com/81630831/203550960-aac25fdf-a90d-4bb4-b846-6c9bac9abada.png

Hey, I also have the same issues. Did you solve it?

— Reply to this email directly, view it on GitHub https://github.com/CloudCompare/CloudComPy/issues/72#issuecomment-1651537346, or unsubscribe https://github.com/notifications/unsubscribe-auth/A3ODLZHASE3QIGAH2FRIR2DXSDYVPANCNFSM6AAAAAAQ5VJTCY . You are receiving this because you modified the open/close state.Message ID: @.***>

[prascle]

Hi, Several users have a similar problem, and I've found a solution for two different cases so far:

1. When there is a space in the path, for example if you install in c:\Program files\CloudComPy310, it doesn't work. Try moving CloudComPy310 to a path without spaces. In my case, I install CloudComPy and conda somewhere under my home directory (with no space in the path).
2. Another case is an old conda CloudComPy310 environment (if you created this environment a long time ago): recreating or updating this environment may solve the problem.

There are certainly other configurations where the problem occurs. To facilitate diagnosis, try running CloudCompare in the conda CloudComPy310 environment, after enCloudComPy.bat (even if envCloudComPy.bat fails). If CloudCompare works, it's probably a PYTHONPATH problem (similar to case #1). If CloudCompare doesn't launch, (e.g. a missing library) it's more likely to be a problem with the conda environment (similar to case #2).

Paul