this post was submitted on 21 Jul 2023
111 points (98.3% liked)

Linux

48031 readers
1225 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
nooter692@lemmy.ml
AgreeableLandscape@lemmy.ml
MarcellusDrum@lemmy.ml
cypherpunks@lemmy.ml
cyclohexane@lemmy.ml
d3Xt3r@lemmy.nz
111
Coders, what is your workflow on Linux (sh.itjust.works)
submitted 1 year ago by Croquette@sh.itjust.works to c/linux@lemmy.ml
117 comments fedilink hide all child comments
 

Hello,

I installed Ubuntu a few months ago on my work laptop and I've been running and loving it since.

However, I am used to VsCode, so this is what I am using in Ubuntu as well.

So I am curious, what kind of coding so you do? And what is your workflow.

I am an embedded firware developper and mainly use C. I am cross compiling my code in VsCode for a FPGA from Xilinx (dual core arm + PL)

Never dove into make files and cmake more than what I needed in the past, but I had an opportunity to learn CMake and build a project from it.

So my workflow is :

  1. Code in VsCode
  2. Build in CMake
  3. Transfer the app through scp on the target with a custom script (target is running petalinux, which is yocto + Xilinx recipes)
  4. Use gdb server to debug the code.

It's a pretty simple workflow, but I'd like to know what you guys are running so that I can maybe upgrade my workflow.

you are viewing a single comment's thread
view the rest of the comments
[–] Solemn@lemmy.dbzer0.com 6 points 1 year ago (1 children)
  1. Setup my vimrc.
  2. Clone the project, and realize that whatever repo managing system they started using 3 years ago requires setup steps not in the README and breaks everything at the slightest touch.
  3. Build the currently relevant project in whatever build system they started using 3 years ago (CMake is quite nice).
  4. Fix my vimrc to be compliant with whatever tabbing they use.
  5. Realize that for some reason, someone made a commit in the file I'm reading that uses 3 space tabs. And worse, someone approved that PR.
  6. Make changes via vim.
  7. Debug via print because setting up gdb or JTAG on embedded systems is usually more effort than its worth.
  8. Realize it's a timing issue and reluctantly go find the JTAG debugger.
[–] Croquette@sh.itjust.works 3 points 1 year ago

It's funny how the JTAG debugger should be the first thing that we use, but just like you, I don't want to use it until really necessary.

But the moment I setup everything, then I wonder why I've waited so long to do the setup haha.