C:\Strawberry\c\bin\cmake.exe could not find libexpat-1.dll

[code4lala]

if I copy C:\Strawberry\c\bin\libexpat-1__.dll to C:\Strawberry\c\bin\libexpat-1.dll, copy the dll file and remove two underlines, cmake.exe would work.

strawberry perl version strawberry-perl-5.40.0.1-64bit.msi

[shawnlaffan]

I am not sure this is a Strawberry Perl issue.

cmake is not distributed with Strawberry Perl 5.40 due to clashes with other packaging systems.

If you are deriving it from elsewhere then you need to ensure it has access to the relevant DLLs it depends on.

[code4lala]

The cmake is from the strawberry perl package, I downloaded the strawberry perl msi from the official site:

https://strawberryperl.com/

https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/SP_54001_64bit_UCRT/strawberry-perl-5.40.0.1-64bit.msi

[mohawk2]

I think cmake being included is a great idea. It just sounds like it needs this double-underscore business including in Strawberry's cmake-visible packaging info.

[shawnlaffan]

I stand corrected. It comes from winlibs and should have been removed before we cut the release.

We could look at building our own cmake but there is an Alien::cmake that works well. That also avoids issues such as SP 5.36 which had an old version of cmake that got in the way of another toolchain (I don't remember all the details at the moment).

See also #154

[mohawk2]

Auditing things sounds like a good idea! But this doesn't seem like a problem with building cmake, only with the info it finds within the distro.

@code4lala can you take us through the steps you took to find this problem? Did you make a local cmake distro, and if so, can you share all the parts of it so we could try that out?

[code4lala]

@mohawk2 sure, it's easy! just download https://github.com/StrawberryPerl/Perl-Dist-Strawberry/releases/download/SP_54001_64bit_UCRT/strawberry-perl-5.40.0.1-64bit.msi and install it! then go to explorer and navigvate to C:\Strawberry\c\bin, double click cmake.exe

[mohawk2]

@code4lala I don't think that is supposed to do very much. It's not a GUI application. When you say it "worked" after the DLL copying, what do you mean?

[code4lala]

@mohawk2 after copying, cmake would not pop up an error window, and it works, I can use it to build my project.

[mohawk2]

@code4lala Can you try undoing the copy/rename, and then using it to build your project? I want to test whether SP5.40 can use its supplied cmake to build projects, and double-clicking it in Explorer isn't part of that.

[shawnlaffan]

I don't have the MSI version installed at the moment but it should be the same as the portable version.

This has libexpat-1.dll and cmake runs without error.

@code4lala - I wonder if your installation has gone wrong somewhere.

\perls\5.40.0.1_PDL\c\bin\cmake
Usage

  cmake [options] <path-to-source>
  cmake [options] <path-to-existing-build>
  cmake [options] -S <path-to-source> -B <path-to-build>

Specify a source directory to (re-)generate a build system for it in the
current working directory.  Specify an existing build directory to
re-generate its build system.

Run 'cmake --help' for more information.

Also, that cmake depends on several more DLLs than libexpat-1.dll. See below.

objdump -x \perls\5.40.0.1_PDL\c\bin\cmake.exe | findstr DLL
 vma:            Hint    Time      Forward  DLL       First
        DLL Name: libarchive-13.dll
        DLL Name: libcurl-4.dll
        DLL Name: libexpat-1.dll
        DLL Name: librhash.dll
        DLL Name: libuv-1.dll
        DLL Name: zlib1.dll
        DLL Name: ADVAPI32.dll
        DLL Name: CRYPT32.dll
        DLL Name: KERNEL32.dll
        DLL Name: api-ms-win-crt-convert-l1-1-0.dll
        DLL Name: api-ms-win-crt-environment-l1-1-0.dll
        DLL Name: api-ms-win-crt-filesystem-l1-1-0.dll
        DLL Name: api-ms-win-crt-heap-l1-1-0.dll
        DLL Name: api-ms-win-crt-locale-l1-1-0.dll
        DLL Name: api-ms-win-crt-math-l1-1-0.dll
        DLL Name: api-ms-win-crt-private-l1-1-0.dll
        DLL Name: api-ms-win-crt-runtime-l1-1-0.dll
        DLL Name: api-ms-win-crt-stdio-l1-1-0.dll
        DLL Name: api-ms-win-crt-string-l1-1-0.dll
        DLL Name: api-ms-win-crt-time-l1-1-0.dll
        DLL Name: api-ms-win-crt-utility-l1-1-0.dll
        DLL Name: ole32.dll
        DLL Name: OLEAUT32.dll
        DLL Name: PSAPI.DLL
        DLL Name: libwinpthread-1.dll
        DLL Name: SHELL32.dll
        DLL Name: USER32.dll
        DLL Name: WS2_32.dll
        DLL Name: libgcc_s_seh-1.dll
        DLL Name: libstdc++-6.dll

[code4lala]

@mohawk2 undoing the copy/rename, and then using it to build your project -> cmake just exit without printing anything.
@shawnlaffan the msi installation didn't report any error.

[shawnlaffan]

There have been no updates to this issue for a while now.

My suspicion is that it is an issue with the user system, possibly mixed paths. Such a situation will not provide an error on installation.

I'll close this in a few days or when I next do a sweep of issues.