User forums > General (but related to Code::Blocks)
building wxWidget on Kubuntu
oBFusCATed:
--- Quote from: devguy on April 17, 2011, 09:45:52 pm ---CodeBlocks needs a painless makefile project importer, I think I am going to stick with NB where I need to import a project using only a makefile. C::B could learn something from NB!
--- End quote ---
Yes, someone should write a project template for custom makefiles, simple as that...
The thing is that C::B assumes that you know what you're doing when dealing with custom makefile projects and so the steps are no problem for you.
Importing makefile projects (turning them in C::B native projects) is pretty much impossible, one should write a make implementation to do it right.
Won't happen in C::B, 99%...
devguy:
--- Quote from: oBFusCATed on April 17, 2011, 10:09:44 pm ---
--- Quote from: devguy on April 17, 2011, 09:45:52 pm ---CodeBlocks needs a painless makefile project importer, I think I am going to stick with NB where I need to import a project using only a makefile. C::B could learn something from NB!
--- End quote ---
Yes, someone should write a project template for custom makefiles, simple as that...
The thing is that C::B assumes that you know what you're doing when dealing with custom makefile projects and so the steps are no problem for you.
Importing makefile projects (turning them in C::B native projects) is pretty much impossible, one should write a make implementation to do it right.
Won't happen in C::B, 99%...
--- End quote ---
well being a Windows software developer, I could also say C::B could assume that I knows what I'm doing with Visual Studio projects, but today there is a importer to make things easy.
I don't know why I need to import a Win32 DLL project so I can work on it from Linux, with all the Win32 compiler pre-processor that don't make sense on Linux, but CB blindly & happily sets up a CB projects anyway.
the "custom" makefile is not something I created, but something someone else created, for CB to assume I know what I am doing is false
I guess what I am getting at, is when the folks at C:B change their language and possibly mindset towards creating a makefile importer, nothing will ever get done and it will always seem impossible, but it's not, unless core knowledge left CB with developers who are no longer a part of this project?
is it possible to have CB just work with a makefile project, i really don't care about having a CB project created, I just want to load said project, build it and then be able to debug the source, the makefile could be left as is.
oBFusCATed:
--- Quote from: devguy on April 17, 2011, 11:05:09 pm ---well being a Windows software developer, I could also say C::B could assume that I knows what I'm doing with Visual Studio projects, but today there is a importer to make things easy.
--- End quote ---
VS projects are easier to parse, way easier, than Makefiles, that is why there is such a feature. (Someone needed it and have contributed the code to C::B)
Makefiles on the other hand are a set of rules and each rule can be arbitrary command, there are variables that can be expanded, also you could have nested Makefiles, pretty complex.
C::B gives you the possibility to use the Makefile unaltered. It is a bit complex to setup at the moment, but it could be simplified with a project template (simple script).
I don't understand what is your problem :lol:
--- Quote from: devguy on April 17, 2011, 11:05:09 pm ---I don't know why I need to import a Win32 DLL project so I can work on it from Linux, with all the Win32 compiler pre-processor that don't make sense on Linux, but CB blindly & happily sets up a CB projects anyway.
--- End quote ---
And the imported project compiles without modifications? I doubt...
--- Quote from: devguy on April 17, 2011, 11:05:09 pm ---the "custom" makefile is not something I created, but something someone else created, for CB to assume I know what I am doing is false
--- End quote ---
I meant that this option is for the people who know what a makefile is and how to write one, so they are comfortable with it and want to use it instead of C::B's native build system.
--- Quote from: devguy on April 17, 2011, 11:05:09 pm ---I guess what I am getting at, is when the folks at C:B change their language and possibly mindset towards creating a makefile importer, nothing will ever get done and it will always seem impossible, but it's not, unless core knowledge left CB with developers who are no longer a part of this project?
--- End quote ---
Hm, it you so desperately need this feature provide a patch?
devguy:
all i wanted to do was be able to build a open source project like wxWidgets and be able to walk through the code, since I am new too all this (on Linux) asking me to provide a patch is kind of pushing it :P ...i'm trying my best just to get started to make contributions to wxWidget project.
also since NB already lets me load up a project from a "custom" makefile, build and debug from it's IDE, its easier to use another tool, it doesn't make sense for me to provide a patch. however if I was a CB developer, i'd worry about making the project more attractive as the go-to IDE 8)
oBFusCATed:
--- Quote from: devguy on April 17, 2011, 11:59:36 pm ---all i wanted to do was be able to build a open source project like wxWidgets and be able to walk through the code, since I am new too all this (on Linux) asking me to provide a patch is kind of pushing it :P ...i'm trying my best just to get started to make contributions to wxWidget project.
--- End quote ---
But you can do it, see the Jens post...
It is not one click job, but 20 clicks, big deal.
p.s. there isn't one IDE to rule them all, unfortunately :)
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version