Hi, Hemant
Thanks for your feedback. It's indeed just like what you described to build vpp. I know how to build vpp. Why to choose vpp 20.09 not the latest version? It's just because our project is set up based on vpp 20.09. For our case, 1) our project ABC dir hierarchy is like this: ├── ABC │ ├── vpp │ │ ├── xxx │ │ └── ... │ ├── apps │ │ ├── xxx │ │ │ ├── xxx │ │ │ │ ├── xxx │ │ │ │ ├── ... 2) when building vpp rpm in the sub-folder "vpp", vpp official build processing captures vpp version info from git tag info via commands "git describe". I regard that is the vpp official naming processing for vpp generated files, such as rpms. 3) vpp has its own tag format like this vXX.XX.X-rcX, eg. v20.09.1-rc0 4) but our project "ABC" has our own tag format like this ABC-XX.XX.XX-rcX, eg. ABC-21.04.01-rc0 5) so, when applying the tag ABC-21.04.01-rc0 for the whole project "ABC", it means the tag format is applied to the sub-folder "vpp" also 6) it causes the tag of our project's "vpp" does not comply with vpp official tag format rule and it causes the vpp "make pkg-rpm" failed 7) so, is there a convenient and elegant way to eliminate vpp official naming processing to customize vpp generated files' name as we demand 8) I have found all the naming processing codes in vpp Makefile and my solution for my case is just to modify them one by one to customize the generated vpp rpm file name 9) but I regard there are a lot of vpp 3rd-party users like us, so I want to know how other vpp 3rd-party users handle the same vpp usage scenario as ours Thanks in advance! Best Regards, Tao Wang ________________________________ From: hem...@mnkcg.com Sent: Wednesday, March 17, 2021 12:36 PM To: Tao Wang; vpp-dev@lists.fd.io Cc: zhiyong.y...@intel.com; zhongbao....@intel.com; shaohe.f...@intel.com; Jinhui Li; Cong Hu Subject: RE: [vpp-dev] Is there a convenient way to name generated files when making VPP, such as rpm Github is just a mirror which may be up to date with latest VPP software and also github is not the correct repo to work with VPP software. Please use the command below to get latest VPP software. git clone https://gerrit.fd.io/r/vpp In vpp root directory, type “sudo make install-deps”. Thereafter, type “sudo make install-ext-deps”. Then, you can build an image using “sudo make build-release”. The README has a note with alternative way to build using vagrant. Hemant From: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> On Behalf Of Tao Wang Sent: Tuesday, March 16, 2021 10:51 PM To: vpp-dev@lists.fd.io Cc: Yang, Zhiyong <zhiyong.y...@intel.com>; Shi, Zhongbao <zhongbao....@intel.com>; Feng, Shaohe <shaohe.f...@intel.com>; Jinhui Li <jinhui...@tietoevry.com>; Cong Hu <cong...@tietoevry.com> Subject: [vpp-dev] Is there a convenient way to name generated files when making VPP, such as rpm Hi, I got VPP code via "git clone -b v20.09 https://github.com/FDio/vpp.git";. When "make pkg-rpm", the generated VPP rpms are named by git tag v20.09 and looked like "vpp-20.09-release.x86_64.rpm". We are using VPP as a sub-project in our project and we have our own git tag format not like VPP's format "vXX.XX-X". If using our tag format for the whole project (include VPP as a sub-folder), it would cause VPP make failed. Is there a convenient way to purify VPP original naming processing (most related with git operations in Makefile) to customize VPP generated files' name as we want? I have found all the naming processing codes in VPP Makefile and I only know to modify them one by one to achieve the goal of customizing VPP generated files' name. So as a VPP 3rd-party user like us, I want to know if there is a more convenient and elegant way to name VPP generated files? Thanks! Best Regards, Tao Wang
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#18963): https://lists.fd.io/g/vpp-dev/message/18963 Mute This Topic: https://lists.fd.io/mt/81394971/21656 Group Owner: vpp-dev+ow...@lists.fd.io Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com] -=-=-=-=-=-=-=-=-=-=-=-
