| CFLAGS = -Wall -g `pkg-config --cflags gtk4` | |
| LDFLAGS = `pkg-config --libs gtk4` | |
| all: main.c | |
| $(CC) -o main main.c $(CFLAGS) $(LDFLAGS) | |
| clean: | |
| rm -f *~ | |
| rm -f *.o | |
| rm -f main |
| CFLAGS = -Wall -g `pkg-config --cflags gtk+-3.0` | |
| LDFLAGS = `pkg-config --libs gtk+-3.0` | |
| all: main.c | |
| $(CC) -o main main.c $(CFLAGS) $(LDFLAGS) | |
| clean: | |
| rm -f *~ | |
| rm -f *.o | |
| rm -f main |
| package FileLogger; | |
| # FileLogger.pm | |
| # Retrieved from: https://www.perltutorial.org/perl-module/ | |
| # Example for using modules in perl. | |
| use strict; | |
| use warnings; | |
| my $LEVEL = 1; # default log level | |
The Gerber format is an open 2D binary vector image file format. It is the standard file used by printed circuit board (PCB) industry software to describe the printed circuit board images: copper layers, solder mask, legend, etc.
Gerber files should be inside a .rar or.zip archive with standard file extensions:
| /* | |
| Forcing inlining is useful if: | |
| - inline is not respected by the compiler (ignored by compiler cost/benefit analyzer), and | |
| - inlining results in a necessary performance boost | |
| For code portability, the following preprocessor directives may be used: | |
| */ | |
| #ifdef _MSC_VER | |
| #define forceinline __forceinline |
Retrieved from: https://www.designnews.com/content/5-tips-setting-realistic-project-expectations/97311123157218
by: Jacob Beningo Embedded Systems Conference - MinneapolisIoT, Consumer Electronics, Electronics & Test, Design Hardware & Software August 01, 2017
Quite a few companies and teams that I encounter have an expectations problem. They have unrealistic expectations for the time and effort that it takes to develop an embedded system. On the spectrum between pessimistic and optimistic, they typically blow past optimistic into the fantasy land zone.
Retrieved from: https://www.designnews.com/electronics-test/top-5-causes-project-fatigue/214387605661501
By: Jacob Beningo in Electronics & Test, Automation & Motion Control on September 12, 2019
There are numerous causes for projects to break down. Here are the five most common.
Project fatigue can have a crippling effect on the project development cycle. A project starts and the development team is energized and dive in with positive fervor,
| CFLAGS = -Wall -g `pkg-config --cflags gtk+-3.0` -lm -lpthread | |
| LDFLAGS = `pkg-config --libs gtk+-3.0` | |
| all: main.c | |
| $(CC) -o main main.c $(CFLAGS) $(LDFLAGS) | |
| clean: | |
| rm -f *~ | |
| rm -f *.o | |
| rm -f main |
| *~ | |
| *.bak | |
| *.asm | |
| *.ihx | |
| *.lnk | |
| *.lst | |
| *.map | |
| *.mem | |
| *.rel | |
| *.rst |
