Expanding Python with C++ modules - Revision history

Davrot: /* Makefile */

2025-10-21T16:04:03Z

Makefile

← Older revision		Revision as of 16:04, 21 October 2025
Line 55:		Line 55:
	If you are programming in C++ and don’t know how to use a Makefile then you really should [https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html look it up].		If you are programming in C++ and don’t know how to use a Makefile then you really should [https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html look it up].

	I am working under Linux and my Makefile looks like ~~[[Makefile\|~~this~~]]…~~ MyModuleCPU.cpp and PyMyModuleCPU.cpp are compiled in .o files and then linked into PyMyModuleCPU. However, Python needs a special filename ending which depends on the Python version. Thus there is this additional copy command dealing with this issue.		I am working under Linux and my Makefile looks like this. MyModuleCPU.cpp and PyMyModuleCPU.cpp are compiled in .o files and then linked into PyMyModuleCPU. However, Python needs a special filename ending which depends on the Python version. Thus there is this additional copy command dealing with this issue.

	== The wrapper file ==		== The wrapper file ==

2025-10-21T16:03:13Z

The test program (test.py)

@@ Line 613: / Line 613: @@
 * Check the properties of a list : bool CheckList(py::list &#x26;Arg_List, int Check_NumberOfDimensions, size_t dType);
-== The test program ([[test.py]]) ==
+== The test program ==
 I think that the mathematical operation that the test code does, need no additional explanation. (A random matrix is multiplied by 5.0)<syntaxhighlight lang="python">X
 [[0.43861361 0.34633103 0.30473636 0.25559892 0.61136669 0.61763177]

2025-10-21T16:01:20Z

The save (and slow) way to communicate (MyModuleCPU.cpp)

2025-10-21T15:59:51Z

The class definition of MyModule

← Older revision		Revision as of 15:59, 21 October 2025
Line 91:		Line 91:

	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">
	<syntaxhighlight lang="h">		<syntaxhighlight lang="cpp">
	#ifndef MYMODULECPU		#ifndef MYMODULECPU
	#define MYMODULECPU		#define MYMODULECPU

2025-10-21T15:58:46Z

The class definition of MyModule (MyModuleCPU.h)

@@ Line 88: / Line 88: @@
 These methods of the class MyModule are defined in MyModuleCPU.h and do what their names suggest they will do…
-== The class definition of MyModule ([[MyModuleCPU.h]]) ==
+== The class definition of MyModule ==
 The exported methods are public. The rest are a collection of methods to handle the data exchange between C++ and Python in a safe way.

2025-10-21T15:57:46Z

The wrapper file (PyMyModuleCPU.cpp)

@@ Line 57: / Line 57: @@
 I am working under Linux and my Makefile looks like [[Makefile|this]]… MyModuleCPU.cpp and PyMyModuleCPU.cpp are compiled in .o files and then linked into PyMyModuleCPU. However, Python needs a special filename ending which depends on the Python version. Thus there is this additional copy command dealing with this issue.
-== The wrapper file ([[PyMyModuleCPU.cpp]]) ==
+== The wrapper file ==
 The wrapper file is the connection point between Python and C++. It tells Python what to call. In this example we have three functions we export into the Python space:

2025-10-21T15:54:28Z

Makefile

← Older revision		Revision as of 15:54, 21 October 2025
Line 13:		Line 13:
	== Makefile ==		== Makefile ==

	~~Makefile~~
	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">
	<syntaxhighlight lang="makefile">		<syntaxhighlight lang="makefile">
Line 51:		Line 50:
	</syntaxhighlight>		</syntaxhighlight>
	</div>		</div>

			Makefile

	If you are programming in C++ and don’t know how to use a Makefile then you really should [https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html look it up].		If you are programming in C++ and don’t know how to use a Makefile then you really should [https://www.gnu.org/software/make/manual/html_node/Simple-Makefile.html look it up].

2025-10-21T15:54:11Z

Makefile

← Older revision		Revision as of 15:54, 21 October 2025
Line 13:		Line 13:
	== Makefile ==		== Makefile ==

			Makefile
	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">
	<syntaxhighlight lang="makefile">		<syntaxhighlight lang="makefile">

2025-10-21T15:53:46Z

A very simple example

← Older revision		Revision as of 15:53, 21 October 2025
Line 6:		Line 6:
	What do we need in the most minimal scenario?		What do we need in the most minimal scenario?

	* ~~[[Media:~~Makefile~~\|Makefile]]~~ plus a .env file		* Makefile plus a .env file
	* Module wrapper ([[PyMyModuleCPU.cpp]])		* Module wrapper (PyMyModuleCPU.cpp)
	* The module ([[MyModuleCPU.cpp]] and [[MyModuleCPU.h]])		* The module (MyModuleCPU.cpp and MyModuleCPU.h)
	* Some test code [[test.py]]		* Some test code test.py

	== Makefile ==		== Makefile ==

2025-10-21T15:53:12Z

Makefile

← Older revision		Revision as of 15:53, 21 October 2025
Line 11:		Line 11:
	* Some test code [[test.py]]		* Some test code [[test.py]]

	== [[Makefile]] ==		== Makefile ==

	<div class="mw-collapsible mw-collapsed">		<div class="mw-collapsible mw-collapsed">