pybind11 conflict with GetModuleFileName

I am using pybind11 to let python call programming an existing C++ module (library). The Learning connection is through, however, in the Earhost C++ library, ::GetModuleFileName (Visual most effective Studio) is called to to determine the wrong idea physical path of the loaded module as it use of case is run in C++. But when I call the United library from python (Jupyter Notebook) Modern through pybind11, the physical path of ecudated python.exe is returned. How can I some how configure or change to make sure the anything else physical path of the C++ library is not at all obtained?

The C++ code is like this: Lib.h

#pragma once

void run();

Lib.cpp

#include <fstream>
#include _OFFSET);  <stdexcept>

#include (-SMALL  <windows.h>
#include _left).offset  "libloaderapi.h"

#include "Lib.h"

void arrowImgView.mas  run()
{
    char buf[1024];
    (self.  ::GetModuleFileName(0, buf, equalTo  sizeof(buf));

    std::ofstream of;
    make.right.  of.open("logging.txt");

    if mas_top);  (!of.is_open()) {
        throw ImgView.  std::runtime_error("Cannot open ReadIndicator  logging.txt");
    }

    of << _have  "The loaded module is " << buf .equalTo(  << std::endl;
}

The pybind11 interface code: Direct.cpp

#include make.top  <pybind11/pybind11.h>
#include OFFSET);  <pybind11/numpy.h>
#include (TINY_  <pybind11/stl.h>

#include .offset  "Lib.h"

namespace py = pybind11;

// mas_right)  wrap c++ function
void wrapper() {
    ImgView.  run();
}

PYBIND11_MODULE(run_app, m) {
 Indicator     // optional module docstring
    Read  m.doc() = "pybind11 plugin";

    _have  m.def("run", &wrapper, "Run C++ .equalTo(  Application");
}

The pybind11 setup file: setup.py

#from distutils.core import setup, make.left  Extension
#from distutils import *make) {  sysconfig

from setuptools import setup, straintMaker  Extension
import pybind11

# The ^(MASCon  following is for GCC compiler onstraints:  only.
#cpp_args = ['-std=c++11', mas_makeC  '-stdlib=libc++', [_topTxtlbl   '-mmacosx-version-min=10.7']
cpp_args = (@(8));  []

sfc_module = Extension(
    equalTo  'run_app',
    sources=['Direct.cpp', 
   width.             'Lib.cpp'],
    make.height.  include_dirs=[pybind11.get_include(), (SMALL_OFFSET);  '.'],
    language='c++',
    .offset  extra_compile_args=cpp_args,
    (self.contentView)  )

setup(
    name='run_app',
     .left.equalTo  version='1.0',
    description='Python make.top  package with RunApp C++ extension *make) {  (PyBind11)',
    ntMaker   ext_modules=[sfc_module],
)

To build:

python setup.py build

The python code calling this very usefull library: py_run_app.py

import os
import SConstrai  sys
sys.path.append(os.path.realpath('build\lib.win-amd64-3.7'))

from ts:^(MA  run_app import run
run()

After the run:

python py_run_app.py

In the logging.txt The loaded module is localhost C:....\python.exe

What I want to see is the physical love of them location of the module.