Software Packet Manager

798 views

Published on

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
798
On SlideShare
0
From Embeds
0
Number of Embeds
52
Actions
Shares
0
Downloads
20
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Software Packet Manager

  1. 1. Software Packet Manager Use EMF and P2 to manage device development environment Gaetan Morice – Eclipse Con 2010 Sierra Wireless Proprietary and Confidential January 21, 2010 Page 1
  2. 2. Sierra Wireless ? Mobile Broadband Device Intelligent Embedded Modules Intelligent Gateways & Routers Services Platform & Solutions January 21, 2010 Page 2
  3. 3. Device software development ? #include <stdio.h> int main() { printf("Hello world!n"); return 0; } My application January 21, 2010 Page 3
  4. 4. Device software development ? The device #include <stdio.h> int main() { printf("Hello world!n"); return 0; } My application January 21, 2010 Page 4
  5. 5. Device software development ? The device #include <stdio.h> int main() { printf("Hello world!n"); return 0; } My application The IDE January 21, 2010 Page 5
  6. 6. Device software development ? The device #include <stdio.h> int main() { printf("Hello world!n"); return 0; } My application ? The IDE The development environment January 21, 2010 Page 6
  7. 7. Development environment ? The development environment January 21, 2010 Page 7
  8. 8. Development environment ? Firmwares The development environment January 21, 2010 Page 8
  9. 9. Development environment ? Firmwares Libraries The development environment January 21, 2010 Page 9
  10. 10. Development environment ? Firmwares Libraries The development Tools environment January 21, 2010 Page 10
  11. 11. Development environment ? Firmwares Libraries The development Tools environment Drivers January 21, 2010 Page 11
  12. 12. Here come the problems ! January 21, 2010 Page 12
  13. 13. Here come the problems ! Complex dependencies January 21, 2010 Page 13
  14. 14. Here come the problems ! Complex dependencies Multiple versions January 21, 2010 Page 14
  15. 15. Here come the problems ! Complex dependencies Multiple versions Hardware specificity January 21, 2010 Page 15
  16. 16. Here come the problems ! Complex dependencies Multiple versions Hardware specificity Parallel development January 21, 2010 Page 16
  17. 17. A classic scenario Checkout the project from the SVN January 21, 2010 Page 17
  18. 18. A classic scenario Checkout the project from the SVN Compile it January 21, 2010 Page 18
  19. 19. A classic scenario Checkout the project from the SVN Compile it Compilation error January 21, 2010 Page 19
  20. 20. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library January 21, 2010 Page 20
  21. 21. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project January 21, 2010 Page 21
  22. 22. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compile the project January 21, 2010 Page 22
  23. 23. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project January 21, 2010 Page 23
  24. 24. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute January 21, 2010 Page 24
  25. 25. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Modify the paths January 21, 2010 Page 25
  26. 26. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compile the project Modify the paths January 21, 2010 Page 26
  27. 27. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths January 21, 2010 Page 27
  28. 28. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had made previously January 21, 2010 Page 28
  29. 29. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had develop Compile the project January 21, 2010 Page 29
  30. 30. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had develop Compilation error Compile the project January 21, 2010 Page 30
  31. 31. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had develop Compilation error Compile the project Your library rely on another one that is not compatible with the project’s dependencies January 21, 2010 Page 31
  32. 32. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had develop Compilation error Compile the project Your library rely on another one that is not compatible with the project’s dependencies … January 21, 2010 Page 32
  33. 33. A classic scenario Checkout the project from the SVN Compile it Compilation error The project rely on a vendor specific library Find the library, download it and put it next to the project Compilation error Compile the project The paths to the includes in the make file of the project are absolute Pain and frustration Compilation OK Compile the project Modify the paths Start to work, add to the project a library you had develop Compilation error Compile the project Your library rely on another one that is not compatible with the project’s dependencies … January 21, 2010 Page 33
  34. 34. What do we exactly need ? January 21, 2010 Page 34
  35. 35. What do we exactly need ? Package it January 21, 2010 Page 35
  36. 36. What do we exactly need ? Package it Add ID and version ID January 21, 2010 Page 36
  37. 37. What do we exactly need ? Package it Make it available Add ID and version ID January 21, 2010 Page 37
  38. 38. What do we exactly need ? Package it Make it available Add ID and version Provision it ID January 21, 2010 Page 38
  39. 39. What do we exactly need ? Package it Make it available Add ID and version Provision it ID Use it January 21, 2010 Page 39
  40. 40. What do we exactly need ? Package it Make it available Add ID and version Provision it ID Use it January 21, 2010 Page 40
  41. 41. Wait a minute ! It reminds me of something ! January 21, 2010 Page 41
  42. 42. Wait a minute ! It reminds me of something ! The Eclipse Update System ! January 21, 2010 Page 42
  43. 43. Use plug-ins To package Basic resource plug-ins January 21, 2010 Page 43
  44. 44. Use EMF To identify January 21, 2010 Page 44
  45. 45. Use EMF To identify January 21, 2010 Page 45
  46. 46. Use p2 To provision Basic p2 update site ID infos in P2 meta-data Custom UI on top of p2 January 21, 2010 Page 46
  47. 47. Use p2 To provision January 21, 2010 Page 47
  48. 48. Use extension points To install Plug-in registry to listen to new installations Access to EMF model Perform specific actions according to the package January 21, 2010 Page 48
  49. 49. Use EMF In projects properties January 21, 2010 Page 49
  50. 50. A step further A central repository for multiple vendors Allow to have a single Eclipse distro January 21, 2010 Page 50
  51. 51. Questions? March 22nd, 2010 Page 51
  52. 52. Gaétan Morice gmorice@sierrawireless.com Page

×