[solved] Export project with shared libraries

1

hi all,
sorry if already told ,is it there a way to export a complete project ( I mean with shared libraries ) as zip file?

2

You mean like right click and zip the entire project folder from your file manager. :stuck_out_tongue:

PS: just saw the note about shared libraries. You do realise that the entire way of handling projects in platformio forces anyone else to use platformio to develop or compile the code even if you give the sources to them. Then platformio.ini file contains the list of libraries it needs to build the project successfully. You are covered on that front.

3

yes… I mean like right click (:scream:) but with shared libraries, what this kind of handling projects forces doesn’t matter to me.:stuck_out_tongue_closed_eyes:
about platformio.ini…I’m sorry to say that I don’t find any information about shared libraries there… only when I build the project in the log screen there are which libraries are needed ,with full path…:smirk:

4

When you install libraries you have several ways of handling it. Once is to use the library manager to install libraries per project or globally. The other way is to specify the libraries in the platformio.ini file. This way the entire project information is stored in the initial file. You can zip it and share it. :slight_smile: hope this helps.

5

Yes this could be a way,(I missed this kind of option installing libraries thank you for the info) but it’s not what I’m looking for…

6

Just navigate to .pioenvs directory in a project and copy *.a files, they are static compilied libraries.

2 Likes
7

Ivan ,would you to marry me? :wink:
Thanks a lot.

1 Like
8

What about headers? How should be project recompiled later?

9

Just make a private library which contains all headers and lib.a (archive).

10

I’ve been following this old thread about sharing libraries between projects and I can’t find any directory named .pioenvs in any of my project directories, even those projects that have built successfully. Where should this directory be located in the project structure?

Regarding *.a files, are they supposed to be in the .pioenvs directory? I do see some of these files located under the Build directory.

Rob

11

This thread is 7 yeras old. Many things have changed during the time.

If you crate a library and compile your project you will get an .a file in the build directory:

“MyLib” (located in /lib/MyLib) will end up as “MyLib.a” in the directory .pio/build/envname/libXXX:

Environment “esp32dev”:

.
├── .pio
│   └── build
│       └── esp32dev
│           └── libcf0
│               ├── MyLib
│               │   ├── MyLib.cpp.d
│               │   └── MyLib.cpp.o
│               └── libMyLib.a
├── include
├── lib
│   ├── MyLib
│   │   ├── src
│   │   │   ├── MyLib.cpp
│   │   │   └── MyLib.h
│   │   └── library.json
├── src
│   └── main.cpp
├── test
└── platformio.ini