From b20b2e8d7f0cabe5f5ab16385b48476397991e5d Mon Sep 17 00:00:00 2001 From: Thomas Walker Lynch Date: Fri, 22 Nov 2024 12:15:35 +0800 Subject: [PATCH] cp assembling environment --- README.md | 5 +- developer/C/server.cli.c | 30 ++++ developer/C/server.lib.c | 102 ++++++++++++ developer/a.out | Bin 0 -> 21800 bytes .../document/RT C coding conventions.html | 153 ++++++++++++++++++ developer/tool/make | 6 + developer/tool/makefile | 18 +++ 7 files changed, 310 insertions(+), 4 deletions(-) create mode 100644 developer/C/server.cli.c create mode 100644 developer/C/server.lib.c create mode 100755 developer/a.out create mode 100644 developer/document/RT C coding conventions.html create mode 100755 developer/tool/make create mode 100644 developer/tool/makefile diff --git a/README.md b/README.md index e505925..c739da3 100644 --- a/README.md +++ b/README.md @@ -1,6 +1,3 @@ -# subu -subservient user tools -Create and run sub-users that share the desktop, but are limited to by unix permission to viewing their own files. +release directory has some resources that are shared among projects -see development/documents/subu.html for a more info. \ No newline at end of file diff --git a/developer/C/server.cli.c b/developer/C/server.cli.c new file mode 100644 index 0000000..78a56ee --- /dev/null +++ b/developer/C/server.cli.c @@ -0,0 +1,30 @@ +/* + * This command implements a simple Unix domain socket server. + * + * Usage: + * server + * + * Description: + * This program creates a Unix domain socket at the specified path + * (defined in `server.lib.c`) and listens for incoming connections. + * When a client sends data, the server logs it to a file and echoes + * a receipt. The server runs until interrupted or an error occurs. + * + * Command-line Options and Arguments: + * None: The program is self-contained and does not accept any + * command-line arguments. All configuration is handled within + * the implementation. + */ + +#define IFACE +#include +#include +#include "server.lib.c" + +int main(int argc, char *argv[]) { + (void)argc; // Suppress unused variable warnings + (void)argv; + + // Call the core server function + return Server·run(); +} diff --git a/developer/C/server.lib.c b/developer/C/server.lib.c new file mode 100644 index 0000000..144c3de --- /dev/null +++ b/developer/C/server.lib.c @@ -0,0 +1,102 @@ +#ifndef IFACE +#define Server·IMPLEMENTATION +#define IFACE +#endif + +#ifndef Server·IFACE +#define Server·IFACE + + // Necessary interface includes + #include + #include + #include + + // Interface prototypes + int Server·run(); + +#endif // Server·IFACE + +#ifdef Server·IMPLEMENTATION + + // Implementation-specific includes + #include + #include + #include + #include + #include + + // Constants + #define Server·SOCKET_PATH "mockup/subu_server_home/subu_server.sock" + #define Server·LOG_PATH "mockup/subu_server_home/server.log" + #define Server·BUFFER_SIZE 256 + + int Server·run() { + int server_fd, client_fd; + struct sockaddr_un address; + char buffer[Server·BUFFER_SIZE]; + FILE *log_file; + + // Open the log file + log_file = fopen(Server·LOG_PATH, "a"); + if (log_file == NULL) { + perror("Error opening log file"); + return EXIT_FAILURE; + } + + // Create the socket + if ((server_fd = socket(AF_UNIX, SOCK_STREAM, 0)) == -1) { + perror("Error creating socket"); + fclose(log_file); + return EXIT_FAILURE; + } + + // Configure socket address + memset(&address, 0, sizeof(address)); + address.sun_family = AF_UNIX; + strncpy(address.sun_path, Server·SOCKET_PATH, sizeof(address.sun_path) - 1); + + // Bind the socket + unlink(Server·SOCKET_PATH); // Remove existing file if present + if (bind(server_fd, (struct sockaddr *)&address, sizeof(address)) == -1) { + perror("Error binding socket"); + fclose(log_file); + close(server_fd); + return EXIT_FAILURE; + } + + // Listen for connections + if (listen(server_fd, 5) == -1) { + perror("Error listening on socket"); + fclose(log_file); + close(server_fd); + return EXIT_FAILURE; + } + + printf("Server running, waiting for connections...\n"); + + // Accept and handle client connections + while ((client_fd = accept(server_fd, NULL, NULL)) != -1) { + ssize_t bytes_read; + + memset(buffer, 0, Server·BUFFER_SIZE); + bytes_read = read(client_fd, buffer, Server·BUFFER_SIZE - 1); + if (bytes_read > 0) { + fprintf(log_file, "Received: %s\n", buffer); + fflush(log_file); + } else if (bytes_read == -1) { + perror("Error reading from client"); + } + + close(client_fd); + } + + // Clean up + perror("Error accepting connection"); + fclose(log_file); + close(server_fd); + unlink(Server·SOCKET_PATH); + + return EXIT_FAILURE; + } + +#endif // Server·IMPLEMENTATION diff --git a/developer/a.out b/developer/a.out new file mode 100755 index 0000000000000000000000000000000000000000..771510f461295db1fc4db436413c48f0f4f64252 GIT binary patch literal 21800 zcmeHPdvqJsnZF}xEcq?Rc{m9)a!4RNEI(orV+hD`oXFrjNJ1b$naI+})<%|8X%rk@ z4Y;rbHcPU*Ezm=oKsgllYZ=bMMT2c3^0&OVgN2E_N{^EYK9sN^ zLhMYolvRP^!9T<~1Vu@~*Ik04pij!V0ZFfg3LJ(?;AtFVOhM%#LDHK}Az2hKAS+Oi z`30NwbSg@m`9p*O4{@+v8dXrq73&LdF$6})D>z%WPeHpL#pYC-&^xtC=qdO)sduM@ zN{>*|^96;T?_!~+;L9=)3aWUL`}FUT@$7L6Jp~0eeVm+n<5F*2>M6JeHYq7cbx_*! zb1U}y)VE3Mb+igQ9jzf=P_SE&nS!dm%b`bc`J_o5=FPIca>v0Zg@ zPWt!$`K^mzdVA5Kc+Ef69WNBl``h+!4w4MDgKUxvC6ZTNhH&DkKjEJ=^+Isg48jY_ z(Cf?4sqUHV440uN%Fv@_=;xQA50#-G06l=eGqr*+lb>75(C3t)FDpZ*zB!ZqYs%2+ z^qxtcW%5>zWz1|gon<*In~G+3v*AQ4#_}oj#GNc2Pv&!@ES}DoDV9q|cbXQ9~zvqlg4UA&z;G+s_A|jZWu^N`4!i&MTE#Y;=Bokc@zhPClu$ z%toiWRqC+O)!0hB9vdA2D5j8&UR$Ix7PisrZ1hbwI-QFuU1g&;C?env8@NT~W<6k74rd(5dIQ|!e(^P9J!|}TarzzId4vybOI8CjlHgWt0 z!fC2F723n-|?~kqv?|maY z@w1bgwhnYocD@*X;f40u2*;ei#7zFZc(8HN=b*wE$se0W_aEMaiB)(NpL9mJsJMiJC}sNb;=#qo)7=%L#wH1!7D8|^{M_ns~)7= zi+uAH;k`dUaRXZMynYWT+NY0wq&|{=^DYt$-}=^m9L8t;fe<^|g6zcPhlN6T@4%_> z#LcHze)iD|iTE^#hxy@t2l)|d(X)gerR>Br;O-rGZ{p_n3i-g%&7^P_S-Bfl_P%i9 zoez}q-$OjS?{+$*M^a=1e?}tz29fv+oS`X+@WiC+$WD?Pg+-FO9a2XLIk6L^@V>W6P zSf60GoEzTvd6J2G7=f0gp1HJ+#1q3yS z>OpG+ckjT-iJMOr8gIWA5j)!43Z)Y^n?phk!ow(u5c^Q#L3;5R?E_y=l5lJo!$c zFi!A)3WZI8fs=(o4DeOJLx6>M3x!EQO0?HYNxNY))5iVU!aA>yZntRryu zfi+$~(K_&d5;V0ZwS-vsXHX~KAZzfiZD_f)vG#i39(Kus3(r};WHH#>RuV7>AI_#j z+t=W~!_{A3#1)W_b(qObLKb!S! z>+Q~TcAdYHZQj-^R|f(k(WtW~wt8D{B$Y~I!C^-Bx+{A-##hExbezAUD-aB}=XU2} zW+vB;=fT?}!-=+3+A@Ptwq;ZAa<-+vx0Cg+?d|y(!L>uZ9UsG9*9Q}u279~NmVw?5 zme_)<#DzpEVWB==i!5`KvRopIM}e(Gv@L5U(^27LN5Dbjb{sTr&q3qowVw_eI`q1} zCED^xXYn18wepzKIpUPLLh=-xNruTjGFQTxWYoB`RgOP1$?TAIRm}>Kr!)F|snl0+ zCOe9!;7l^g*M%SBv+{Mjtn)nhB*r1Ki1$3CpM0H$Q%W--{~CryAx{sSP*P(pM{L>+kqMvvFT|m~q_@s_450ZoWL^&`G_+JLgHYAGs939_Cn#K1?c_w2 z39_f^736wV8|YP4TR^Xw-GiKBIOh(!D)^Xw8R?&P+U3CNvY`3(r_Q<-H0>xP^?%UG zJ`gf=q$UF3VvXGZwdDL~P^jrcp`O)60aD)6&$=HpZ7!6(i==WL%z6Vg#Bd3{$CTbq z=JtDffO#G!E03d8N0-ajeVx8OsA<;%@h$hp0hso6uzf44?<1OaKjkYq;@AEe_4#@@ z(xQEl#4g}SK-)lKy&PGl4UpJ{9O=;L8sxi(BR$#+q_c`6A?-sF3vnc@eTk4hj%?Ca zlFn+5T&3+NWX;^G;pYzR1`=C4+W<1E8H9wn*BR|8LIycvY3ETrm)2TP9oK3ISwD+n zzeoEiiEU`S3dn65Er^Ncy9J#4G;06dqNydDaMi-N$s^uANgGNHY$C_qxoI{+JXalyMz@tDs| zDjDv^EsE;mC32N{=nV2cfl}SoZZ7pjk|KwguL@cH{s!vBM~F%V&T{pk#C*R%R==u& z9Q;?}b5FU?g1-heqlHEX z_krWLR4)T_NeyWMy{Y;Q(3jRyt*!&33$AVsK^py>=P>*n3L6{gXt@sHY*269ad#&G4ZyHL!?7ktt11eQtI-Sh7>z?-=KCu&M{CiE;&erO;8jrF_d}wA_^ty<_m_bz zAhPSg4so!UR?plGy|owCUQj#O+=EHIOJ{@4P+Y=lYcH;K<3izSWVNk6BIm-k^5Ld~Qa+p!Tf!gUuJs*C6gIl3{(CT-{ApS~XFps|A5>MV;+1RI6!&&7@k_ zthpO%YlUM(s9(w5YG{V;Me`B;Gdb>W(v~(f*SZ%iT-2n^^7?TX(FAv4YL;w(57#aa zj9pw?ixy5BoXwrDVr&jCpqtE{ZXHfxxW!tE4dCq(t(spX@|aPzp_ZF?gBR3lgrfUU zJ77SYj-sm=MYk^7-`YY!rvP|9+6;Z#|Ekg&g&SUS@FNknd&AB_-_dcorB1GC+HV@_ z34lm*NE8-%sSjU_e+d61{>;uZGP@!9&!>V2CymkjP-T#E{^R?^Vyxwq7pZk#RV=j;8i|gKz zgL=c$y8e*f;+xR*1HNbU>VuMdo9^9y@M%)0mI^;BQuGJ)+6Q&-HTrC*)%c#)tMka3 zUIWy<59;&X)|d4jS%>cSfBE3k2lcu`x_i3|FNbQ|;3!3FIpB=Z!VwhF;*oLF*rxG} zheuzG)~S=wJx|kXrgZHfw=7>3l1ypWsQ7_3k>Ju#&860 z85+3t*ok)t#V)X6?aqKU7Rl~3vpFtF8?d|vBc3(QteG>QtKM}alV&c*hIdGZwKT#kkVp;BDG6aQUXb{>uioqRtV6@4Xj; zNL%FyJ6f`$8@}=vNabswhLMTH&S$xNO14G47z&T#rfNywm7+PN0?TJ)0nMdTgtVG&}6L{OWgn|W*QUZyz z(}`P3$IHpFm>Ca_GR^}O=bJ3hsf%JhMYxsCM=d_ma4eQca~Aq&OtA5o1r-n})8c~! zuwqQmB@mO}k?6AGVZWf;!IFgQFD^G8_JBLY=>eXLcduuXKOKA*YhY?EL5j0QlD@ww zq(~fgNxE7`RZN<|YFH(`DHP%)@{iJ1{54vAlxsv?Y7rx2*I^aC z8UdN55F0$R4E=&K^oKzYuogBhfbK^>r}vfYX(`FO8rUXzzF>mO)1%yeLvii!Oi5oQ?KqFiAlbor zp{6!!?P~+4OJy6NRfw7V|4bP=Eg;M!e=q1wm>WCW^%atL)uGWLTdj;eR>lsCX06U( z8rM6l78_P%gb2gtNFoJd3=^Ia`Zz<@u*M90mm!5g)-YmeVKL$IKGA45t!CB%6)w#(c`k?q>09WDM8b{MguTsMs)r7K=+n#r!XbD+oqf ziHKnr-r|DK8?Y8rr~zYO!y3b2#+vOL`qmF(USQx#Y7B%8!40q3%#3wI8&~%Y85`HG z-7>J%*xI*xXaE|{&r^id2Pg263Gr=XR8I0`@7V<7*hu&83aeNGgUoBA;nkc%0CnS)BY(M~Njd11lkk zxo<3q*)1jt5lpMa%Da(C&?IR%my@3H83WDZO4Rw>zJww^9a2IPk202!3}fs1eswIV zJIIS~i4Y6sc8_6V1!!dj991REY0Yeg1^NC5W<9}7mZm1wZX0PhpTPHX5-~~YTRqrD zCqR(IM8OJ|cGSvKD2#uQ< zdNIcksl^@Q1@-+cwLdG_Tvn9{o`F9to+y zFv{wBq{xE~eKntZ0BcH=0z9A2ocdRS^(*YbD*q>C{gYB(wI3@oJURW3fQn_EV*8Iv z{o_)fuP%a5ZPf5r`m{_!DSFMg*(U)Aqy|GiRwwKS;q*$+#FQQ2TZ zv5NMQ_&o?3i75NU>o2A-l+?UHU?1&24}f9U56J6xK+HMOF1F+_bWvSm7anwDBJbb{la*MP;eeElC>uv2xLq7ujbh|eM0?uS-%u7 znpXPP7Ac~j>Q|6fDyeR#{_B#kQ3*;r3RRHyz|^rJkv%&?Tyj|#2aGm|?8zCA3&D4Y zaPj1Fp|!)VjIvYq(lYwrllo5-2PR?2slTm^{%3oI{J%RC94L#G(ZA**p?{}C!GW@j z)OW`Jr>lhiS5(IkXtDju&W&aC@8}Z>XDGok`ou1dT~da?Kx@Wd^?P;w ktOm{DA}EaQSjPeTM~88TJGj@KS^u<4h5p?R1qaIh4|$cJUjP6A literal 0 HcmV?d00001 diff --git a/developer/document/RT C coding conventions.html b/developer/document/RT C coding conventions.html new file mode 100644 index 0000000..5c0005d --- /dev/null +++ b/developer/document/RT C coding conventions.html @@ -0,0 +1,153 @@ + + + + + + + RT C coding conventions + + + + +
+
+

Reasoning Technology (RT) C coding conventions

+

© 2024 Thomas Walker Lynch - All Rights Reserved.

+
+ +

Introduction

+ +

This document summarizes some of the coding conventions used in RT C projects. Discussed here are conventions for integrated header designs, ad hoc namespaces, and a structured approach to source file extensions. The document also outlines the associated build process using a standardized makefile.

+ +

Header file integration

+ +

RT C projects adopt an innovative approach by integrating headers directly into source files. This ensures consistency between interfaces and implementations, eliminating mismatches. Each file contains both an interface and an implementation section, gated by preprocessor directives.

+ +

Each RT C source file integrates its header directly into the source file. This locality makes header content easier to maintain as everything is found in a single file. It also eliminates the need to maintain two files for each module.

+ +

Each file has two sections

+
    +
  • Interface section: Contains declarations, macros, and #includes needed for the interface. Ensures consistency by defining the interface exactly once, even when the file is included multiple times.
    • +
  • Implementation section: Contains function definitions and additional includes needed for the implementation. This section is compiled only when the file is used as an implementation.
    • +
+ +

Each section is turned on and off with the CPP macro IFACE.

+ +

Example

+ 

+// If not an IFACE, then an IMPLEMENTATION
+#ifndef IFACE
+  #define MyModule·IMPLEMENTATION
+  // Ensures included files are processed for their interfaces.
+  #define IFACE
+#endif
+
+// Define the interface exactly once.
+#ifndef MyModule·IFACE
+#define MyModule·IFACE
+  // Interface-only includes go here.
+  void MyModule·function();
+#endif
+
+#ifdef MyModule·IMPLEMENTATION
+  // Additional includes for implementation go here.
+  #include 
+  void MyModule·function() {
+    printf("Hello, World!\n");
+  }
+#endif
+
+ +

Explanation

+

The example above demonstrates the structure and purpose of each block:

+

First block: Ensures that the file operates correctly based on the value of IFACE. If IFACE is undefined, it defines MyModule·IMPLEMENTATION to enable the implementation section and sets IFACE to ensure subsequent includes process interface sections.

+

Second block: Defines the interface, including declarations and interface-specific includes. The #ifndef MyModule·IFACE macro ensures the interface is defined exactly once, regardless of how many times the file is included.

+

Third block: Contains implementation-specific includes and function definitions. Guarded by MyModule·IMPLEMENTATION, it is only included when compiling the implementation.

+

Interface includes are placed in the interface block, ensuring they are available wherever the interface is used. Implementation includes are isolated in the implementation block, minimizing unnecessary dependencies in other files.

+ +

Namespace conventions

+

RT projects use ad hoc namespaces to maintain clarity and prevent naming conflicts. This is achieved by prefixing exported identifiers with a module-specific name followed by the · (cdot) character.

+ +

Conventions

+
    +
  • Prefix: The module name serves as the prefix, ensuring all identifiers are unique across the program.
    • +
  • Separator: The · character visually separates the prefix from the identifier name, maintaining readability and avoiding conflicts.
    • +
+ +

Example

+ 

+void Server·run();
+
+ +

Source file extensions

+

RT projects use standardized extensions to distinguish between library and command-line interface (CLI) source files:

+
    +
  • .lib.c: Files implementing library functions.
    • +
  • .cli.c: Files implementing command-line tools.
    • +
+ +

The .lib.c files compile into libraries, while .cli.c files compile into standalone executables. The makefile processes these files automatically, ensuring a clear separation of functionality.

+ +

Build process

+

The build process follows these steps:

+
    +
  1. Dependency generation: Run make dependency to create dependencies. This step is only required when the dependency structure changes.
    2. +
  2. Compilation: Run make cli to compile CLI sources and link them against the library. The makefile automatically manages targets and dependencies.
    3. +
+ +

Benefits

+
    +
  • Consistency: Integrated headers ensure interface and implementation are always in sync.
    • +
  • Modularity: Each file encapsulates its interface and implementation, reducing coupling.
    • +
  • Clarity: Ad hoc namespaces and standardized extensions improve readability and organization.
    • +
  • Efficiency: The makefile automates builds, minimizing errors and streamlining development.
    • +
+ +

Conclusion

+

This document outlines the conventions and practices for writing and building RT C projects. By integrating headers, adopting namespaces, and standardizing extensions, RT ensures its projects are robust, modular, and easy to maintain.

+
+ + diff --git a/developer/tool/make b/developer/tool/make new file mode 100755 index 0000000..5ab34eb --- /dev/null +++ b/developer/tool/make @@ -0,0 +1,6 @@ +#!/bin/env /bin/bash + +set -e +cd ${REPO_HOME}/developer +/bin/make -f tool/makefile $@ + diff --git a/developer/tool/makefile b/developer/tool/makefile new file mode 100644 index 0000000..e2af188 --- /dev/null +++ b/developer/tool/makefile @@ -0,0 +1,18 @@ +# /bin/make must be run from $REPO_HOME/developer + +RESOURCE := $(REPO_HOME)/tool_shared/third_party/resource/release/make +include $(RESOURCE)/makefile-environment + +# overriding defaults +EXECDIR=mockup/subu_server_home +LIBDIR=scratchpad + +# assign a compiler to use +C=gcc +CFLAGS= -include "$(RESOURCE)/environment.h" -std=gnu18 -Werror -O0 -ggdb -DDEBUG -DDEBUGDB -I$(INCDIR) +LINKFLAGS=-L$(LIBDIR) -L/usr/lib -L/usr/lib64 -l$(PROJECT) + +# Import the rules. The dash prefix means to ignore include errors. This is +# required because the DEPFILE might not exist yet. +-include $(DEPFILE) +include $(RESOURCE)/makefile -- 2.20.1