I think this is likely to be a bug with Inline/Apache. When you use Inline::C what happens under the covers the first time you run it is rather complicated. In a nutshell your code gets parsed, converted to XS/C and then that gets compiled. The generated XC/C is found in cwd/_Inline/build/script_name_xxxx/. The actual executable objects are found in cwd/_Inline/lib/script_name_xxxx/ where the xxxx is the same as the build name.

At runtime Inline looks to see if it needs to be compiled, and if so runs a compile then execute. If it has already been compiled it just executes.

I can see multiple issues. First if you have run it you should not need cl.exe as it has already been compiled. The fact that your browser can't find cl.exe but you obviously can (it runs from the command line) indicates you are running with different paths to the web server.

Anyway the server/perl should not need to compile this once it has been run off the command line once. If you look at the can't load statement you will see an issue with the path - it has \ and / path separators. As you checked to ensure sunucuya_yukle_cgi_485e.dll is there I wounder if a quick hack in Dynaloader to change the \ to / would fix it?

    foreach (@INC) {
    
        s!\\!/!g;                       # apachify path Win32
        my $dir = "$_/auto/$modpname";  # here is the \ / problem
    
    next unless -d $dir; # skip over uninteresting directories
    
    # check for common cases to avoid autoload of dl_findfile
    my $try =  "$dir/$modfname.dll";
[download]