Re: [Kicad-developers] Build problem of current master tree
On 2021-01-02 9:45 a.m., Jeff Young wrote: Hi Carsten, Known problem when building 5.99 in a tree that used to hold 5.1. Try: cd include rm *_lexer.h Another option would be to issue the command "git clean -x -df" to remove all files that are not part of the source tree. -- Cheers! Kevin. http://www.ve3syb.ca/ | "Nerds make the shiny things that https://www.patreon.com/KevinCozens | distract the mouth-breathers, and | that's why we're powerful" Owner of Elecraft K2 #2172 | #include | --Chris Hardwick ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
On 1/2/21 6:31 PM, jp charras wrote: > > Le 02/01/2021 à 18:11, Carsten Schoenert a écrit : >> Am 02.01.21 um 18:07 schrieb jp charras: >>> What is the problem with these files? >> They are build in tree in case you do a configure out of tree? >> >>> They are already the final header files built from the corresponding .md >>> files. >> In my eyes it's simply the wrong way to build files in another place >> than I do configuring things, that's not expected by the user. > > These files encode the md strings in .md source files. They where > previously html encoded strings inside .h files. I know it's not always obvious what is part of the source and what is the result of the build, so there will be some... borderline cases. But maybe they should not be deleted by a "make clean" then if they are included in the git repo and will be recreated in the source tree after deletion? I'm not a kicad developer, so take this with a few grains of salt, but I had the impression this discussion was going around in circles, so... Cheers, Heiko -- eMails verschlüsseln mit PGP - privacy is your right! Mein PGP-Key zur Verifizierung: http://pgp.mit.edu OpenPGP_signature Description: OpenPGP digital signature ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Le 02/01/2021 à 18:11, Carsten Schoenert a écrit : Am 02.01.21 um 18:07 schrieb jp charras: What is the problem with these files? They are build in tree in case you do a configure out of tree? They are already the final header files built from the corresponding .md files. In my eyes it's simply the wrong way to build files in another place than I do configuring things, that's not expected by the user. These files encode the md strings in .md source files. They where previously html encoded strings inside .h files. But html strings are extremely hard to translate, and where replaced by md strings. The reason they are inside the source is *exactly* the same as we have also the .cpp icon files in sources. All these files are automatically created from .md files or .svg files, and I do not remember any issue about them. But we certainly cannot expect a "user" who just translate strings to be able to build and compile Kicad. This is not (as you know) a basic thing. We also cannot expect a guy who try to build Kicad to also install (and perhaps build) the tools to create the .cpp icons files from the .svg files. Users and developers are not always the same guys and do not have the same skill. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Am 02.01.21 um 18:07 schrieb jp charras: > What is the problem with these files? They are build in tree in case you do a configure out of tree? > They are already the final header files built from the corresponding .md > files. In my eyes it's simply the wrong way to build files in another place than I do configuring things, that's not expected by the user. -- Regards Carsten Schönert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hi, Am 02.01.21 um 17:17 schrieb jp charras: > > Le 02/01/2021 à 17:09, Nick Østergaard a écrit : >> FYI, there are still generated files in the source which are also >> checked in to the source tree: >> >> After a make clean: >> deleted: ../eeschema/dialogs/dialog_bom_help_md.h >> deleted: ../pcb_calculator/attenuators/bridget_tee_formula.h >> deleted: ../pcb_calculator/attenuators/pi_formula.h >> deleted: ../pcb_calculator/attenuators/splitter_formula.h >> deleted: ../pcb_calculator/attenuators/tee_formula.h >> deleted: ../pcb_calculator/eserie_help.h >> deleted: ../pcb_calculator/tracks_width_versus_current_formula.h >> > > They are automatically generated but they must be available in sources > because they are needed for translations. can't they turned into something like '*foo_header.h.in' that get than processed into the final header file? By this the files are still available, or better their content, for localization. -- Regards Carsten Schönert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hello Seth, Am 02.01.21 um 17:02 schrieb Seth Hillbrand: > Hello Carsten- > > We agree with you. This is why we moved the generated files to the > build tree and out of the source tree. But legacy files in the source > tree are still considered first, so older build directories need the > fix-up that Jeff mentioned. We might be able to get around this by > changing the .gitignore but we haven't tested that. thanks, good to you you are aware about this problem. I can remember we had in the past already some posts about this header file thing. -- Regards Carsten Schönert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Le 02/01/2021 à 17:09, Nick Østergaard a écrit : FYI, there are still generated files in the source which are also checked in to the source tree: After a make clean: deleted: ../eeschema/dialogs/dialog_bom_help_md.h deleted: ../pcb_calculator/attenuators/bridget_tee_formula.h deleted: ../pcb_calculator/attenuators/pi_formula.h deleted: ../pcb_calculator/attenuators/splitter_formula.h deleted: ../pcb_calculator/attenuators/tee_formula.h deleted: ../pcb_calculator/eserie_help.h deleted: ../pcb_calculator/tracks_width_versus_current_formula.h They are automatically generated but they must be available in sources because they are needed for translations. -- Jean-Pierre CHARRAS ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
FYI, there are still generated files in the source which are also checked in to the source tree: After a make clean: deleted:../eeschema/dialogs/dialog_bom_help_md.h deleted:../pcb_calculator/attenuators/bridget_tee_formula.h deleted:../pcb_calculator/attenuators/pi_formula.h deleted:../pcb_calculator/attenuators/splitter_formula.h deleted:../pcb_calculator/attenuators/tee_formula.h deleted:../pcb_calculator/eserie_help.h deleted:../pcb_calculator/tracks_width_versus_current_formula.h On Sat, 2 Jan 2021 at 17:03, Seth Hillbrand wrote: > Hello Carsten- > > We agree with you. This is why we moved the generated files to the build > tree and out of the source tree. But legacy files in the source tree are > still considered first, so older build directories need the fix-up that > Jeff mentioned. We might be able to get around this by changing the > .gitignore but we haven't tested that. > > Regards- > Seth > > On Sat, Jan 2, 2021 at 7:07 AM Carsten Schoenert > wrote: > >> Hello Jeff, >> >> Am 02.01.21 um 15:45 schrieb Jeff Young: >> > Hi Carsten, >> > >> > Known problem when building 5.99 in a tree that used to hold 5.1. >> > >> > Try: >> > >> > cd include >> > rm *_lexer.h >> ahh, yes that fixed the build. >> >> But I see the build of additional required files within the source tree >> rather as issue if I build out of tree. Is this behavior a problem of >> cmake or more a miss configuration of the build controlling? >> >> -- >> Mit freundlichen Grüßen >> Carsten Schönert >> >> ___ >> Mailing list: https://launchpad.net/~kicad-developers >> Post to : kicad-developers@lists.launchpad.net >> Unsubscribe : https://launchpad.net/~kicad-developers >> More help : https://help.launchpad.net/ListHelp >> > > > -- > [image: KiCad Services Corporation Logo] > Seth Hillbrand > *Lead Developer* > +1-530-302-5483 > Long Beach, CA > www.kipro-pcb.comi...@kipro-pcb.com > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hello Carsten- We agree with you. This is why we moved the generated files to the build tree and out of the source tree. But legacy files in the source tree are still considered first, so older build directories need the fix-up that Jeff mentioned. We might be able to get around this by changing the .gitignore but we haven't tested that. Regards- Seth On Sat, Jan 2, 2021 at 7:07 AM Carsten Schoenert wrote: > Hello Jeff, > > Am 02.01.21 um 15:45 schrieb Jeff Young: > > Hi Carsten, > > > > Known problem when building 5.99 in a tree that used to hold 5.1. > > > > Try: > > > > cd include > > rm *_lexer.h > ahh, yes that fixed the build. > > But I see the build of additional required files within the source tree > rather as issue if I build out of tree. Is this behavior a problem of > cmake or more a miss configuration of the build controlling? > > -- > Mit freundlichen Grüßen > Carsten Schönert > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp > -- [image: KiCad Services Corporation Logo] Seth Hillbrand *Lead Developer* +1-530-302-5483 Long Beach, CA www.kipro-pcb.comi...@kipro-pcb.com ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
I’m a 3rd-grader (at best) when it comes to cmake/build systems, so I’ll leave that one for others…. > On 2 Jan 2021, at 15:06, Carsten Schoenert wrote: > > Hello Jeff, > > Am 02.01.21 um 15:45 schrieb Jeff Young: >> Hi Carsten, >> >> Known problem when building 5.99 in a tree that used to hold 5.1. >> >> Try: >> >> cd include >> rm *_lexer.h > ahh, yes that fixed the build. > > But I see the build of additional required files within the source tree > rather as issue if I build out of tree. Is this behavior a problem of > cmake or more a miss configuration of the build controlling? > > -- > Mit freundlichen Grüßen > Carsten Schönert > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hello Jeff, Am 02.01.21 um 15:45 schrieb Jeff Young: > Hi Carsten, > > Known problem when building 5.99 in a tree that used to hold 5.1. > > Try: > > cd include > rm *_lexer.h ahh, yes that fixed the build. But I see the build of additional required files within the source tree rather as issue if I build out of tree. Is this behavior a problem of cmake or more a miss configuration of the build controlling? -- Mit freundlichen Grüßen Carsten Schönert ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
Re: [Kicad-developers] Build problem of current master tree
Hi Carsten, Known problem when building 5.99 in a tree that used to hold 5.1. Try: cd include rm *_lexer.h Cheers, Jeff. > On 2 Jan 2021, at 14:00, Carsten Schoenert wrote: > > Hi, > > since a long time I'm trying to build a current version of 5.99 again. > But my attempt is failing with this error. > >> [ 70%] Built target eeschema_kiface_objects >> Scanning dependencies of target eeschema_kiface >> [ 70%] Building CXX object >> eeschema/CMakeFiles/eeschema_kiface.dir/eeschema.cpp.o >> /home/carsten/gitprojects/kicad-upstream/kicad/pcbnew/netlist_reader/kicad_netlist_reader.cpp:239:22: >> error: use of undeclared identifier 'T_pinfunction' >>case T_pinfunction: >> ^ >> /home/carsten/gitprojects/kicad-upstream/kicad/pcbnew/netlist_reader/kicad_netlist_reader.cpp:362:14: >> error: use of undeclared identifier 'T_property' >>case T_property: >> ^ >> 2 errors generated. >> make[2]: *** [common/CMakeFiles/pcbcommon.dir/build.make:689: >> common/CMakeFiles/pcbcommon.dir/__/pcbnew/netlist_reader/kicad_netlist_reader.cpp.o] >> Error 1 >> make[2]: *** Waiting for unfinished jobs >> [ 70%] Linking CXX shared module _eeschema.kiface >> make[1]: *** [CMakeFiles/Makefile2:2859: >> common/CMakeFiles/pcbcommon.dir/all] Error 2 >> make[1]: *** Waiting for unfinished jobs >> [ 70%] Built target eeschema_kiface >> make: *** [Makefile:182: all] Error 2 > > I'm running the required configuration within the classical subfolder > build/ which is empty before starting the cmake call. > > Known problem or do I miss some thing on my site? > > -- > Regrads > Carsten > > ___ > Mailing list: https://launchpad.net/~kicad-developers > Post to : kicad-developers@lists.launchpad.net > Unsubscribe : https://launchpad.net/~kicad-developers > More help : https://help.launchpad.net/ListHelp ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
[Kicad-developers] Build problem of current master tree
Hi, since a long time I'm trying to build a current version of 5.99 again. But my attempt is failing with this error. > [ 70%] Built target eeschema_kiface_objects > Scanning dependencies of target eeschema_kiface > [ 70%] Building CXX object > eeschema/CMakeFiles/eeschema_kiface.dir/eeschema.cpp.o > /home/carsten/gitprojects/kicad-upstream/kicad/pcbnew/netlist_reader/kicad_netlist_reader.cpp:239:22: > error: use of undeclared identifier 'T_pinfunction' > case T_pinfunction: > ^ > /home/carsten/gitprojects/kicad-upstream/kicad/pcbnew/netlist_reader/kicad_netlist_reader.cpp:362:14: > error: use of undeclared identifier 'T_property' > case T_property: > ^ > 2 errors generated. > make[2]: *** [common/CMakeFiles/pcbcommon.dir/build.make:689: > common/CMakeFiles/pcbcommon.dir/__/pcbnew/netlist_reader/kicad_netlist_reader.cpp.o] > Error 1 > make[2]: *** Waiting for unfinished jobs > [ 70%] Linking CXX shared module _eeschema.kiface > make[1]: *** [CMakeFiles/Makefile2:2859: common/CMakeFiles/pcbcommon.dir/all] > Error 2 > make[1]: *** Waiting for unfinished jobs > [ 70%] Built target eeschema_kiface > make: *** [Makefile:182: all] Error 2 I'm running the required configuration within the classical subfolder build/ which is empty before starting the cmake call. Known problem or do I miss some thing on my site? -- Regrads Carsten ___ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp