How houssam142/1337-projects works
Project type and purpose
• This repository, “1337-projects,” is a monorepo grouping eight independent C projects from the 42/1337 curriculum:
• libft – a custom C standard library
• get_next_line – a line-reader utility
• ft_printf – a printf re-implementation with its own tester
• FdF – a 3D wireframe map viewer (uses MLX)
• so_long – a simple 2D maze-style game (uses MLX, includes textures)
• push_swap – a constrained sorting algorithm challenge
• philosophers – the Dining Philosophers concurrency exercise
• minishell – a miniature Unix shell
File structure
• Top-level directories correspond one-to-one with subprojects.
• Reusable libraries live in their own modules: libft, get_next_line, ft_printf.
• Each application has a Makefile, source (.c) and header (.h) files, and in some cases assets (so_long/texture, so_long/maps) or tests (ft_printf/printfTester).
• No cross-project build script; each module builds itself.
• Graphics apps (FdF, so_long) depend on the external MLX library.
README for additional insights
• README only names the repo; it does not detail architecture.
• The absence of a cross-module orchestration suggests each project is self-contained.
a. Main components
• Repository root (container)
• Library modules: libft, get_next_line, ft_printf
• Executable modules: minishell, push_swap, philosophers, FdF, so_long
• Testing module: ft_printf/printfTester
• External Dependency: MLX (graphics), standard C library
• Assets: so_long textures, maps files
b. Relationships and interactions
• Tests module → ft_printf
c. Architectural patterns / design principles
• Monorepo with side-by-side modules
• Clear separation of concerns: core libraries vs standalone apps vs tests
• Each module adheres to a simple Makefile-driven build
d. Key technologies and libraries
• C99 (gcc)
• Makefiles
• MLX (X11 binding) for FdF & so_long
• POSIX (read/write, fork/exec in minishell)
• pthreads or concurrency primitives in philosophers
Detailed capture of essential elements
• Don’t just list folders—show their relationships.
• “libft” and “get_next_line” as reusable core layers.
• That each application layer sits on those core layers and, for two of them, on MLX.
• PrintfTester as a QA component linked to ft_printf.