1. 09 10月, 2013 1 次提交
  2. 30 1月, 2013 1 次提交
  3. 25 7月, 2011 1 次提交
  4. 07 6月, 2011 1 次提交
  5. 25 5月, 2011 1 次提交
  6. 20 9月, 2010 2 次提交
  7. 06 9月, 2010 1 次提交
  8. 01 9月, 2010 1 次提交
    • A
      kconfig qconf: port to QT4 · 133c5f7c
      Alexander Stein 提交于
      A straight forward port to QT4 using qt3to4 and compiling against
        qt3support
      
      * Use pkg-config to detect QT4 which is hopefully portable enough
      * If no QT4, QT3 will by tried instead
      * Classes renamed using qt3to4
        * If build using QT3 renamed to QT3 class names using defines
      * ConfigInfoView::menu has to be renamed as QT4 moc strips struct from
        struct menu and creates a name conflict
      * QT2 support has been dropped
      * The hidden options inserted in 39a4897c
        are use in native API
      Signed-off-by: NAlexander Stein <alexander.stein@informatik.tu-chemnitz.de>
      Signed-off-by: NMichal Marek <mmarek@suse.cz>
      133c5f7c
  9. 02 6月, 2010 3 次提交
  10. 20 9月, 2009 1 次提交
  11. 10 6月, 2009 5 次提交
    • M
      kconfig: do not hardcode ".config" filename · 284026cd
      Markus Heidelberg 提交于
      Rather than hardcoding ".config" use conf_get_configname(), which also
      respects the environment variable KCONFIG_CONFIG.
      
      This fixes "make silentoldconfig" when KCONFIG_CONFIG is used and also
      suggests the given filename for "Load" and "Save as" in qconf.
      Signed-off-by: NMarkus Heidelberg <markus.heidelberg@web.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      284026cd
    • M
      kconfig qconf: fix the type of the desktop widget · 8d90c97e
      Markus Heidelberg 提交于
      QApplication::desktop() returns a pointer to QDesktopWidget, not to
      QWidget.
      
      Fixes the following compiler error after a quick conversion with 'qt3to4',
      which occured with g++ 3.4.6 and 4.1.2, but not anymore with 4.3.2.
      
      scripts/kconfig/qconf.cc: In constructor 'ConfigMainWindow::ConfigMainWindow()':
      scripts/kconfig/qconf.cc:1289: error: cannot convert 'QDesktopWidget*' to 'QWidget*' in initialization
      Signed-off-by: NMarkus Heidelberg <markus.heidelberg@web.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      8d90c97e
    • M
      kconfig qconf: add namespace for use of Key_ enum values · fbb86374
      Markus Heidelberg 提交于
      They are defined in the 'Qt' namespace.
      
      Fixes the following compiler errors after a quick conversion with 'qt3to4',
      which occured with g++ 3.4.6 and 4.1.2, but not anymore with 4.3.2.
      
      scripts/kconfig/qconf.cc: In member function 'virtual void ConfigLineEdit::keyPressEvent(QKeyEvent*)':
      scripts/kconfig/qconf.cc:311: error: 'Key_Escape' was not declared in this scope
      scripts/kconfig/qconf.cc:313: error: 'Key_Return' was not declared in this scope
      scripts/kconfig/qconf.cc:314: error: 'Key_Enter' was not declared in this scope
      
      scripts/kconfig/qconf.cc: In member function 'virtual void ConfigList::keyPressEvent(QKeyEvent*)':
      scripts/kconfig/qconf.cc:653: error: 'Key_Escape' was not declared in this scope
      scripts/kconfig/qconf.cc:666: error: 'Key_Return' was not declared in this scope
      scripts/kconfig/qconf.cc:667: error: 'Key_Enter' was not declared in this scope
      scripts/kconfig/qconf.cc:681: error: 'Key_Space' was not declared in this scope
      scripts/kconfig/qconf.cc:684: error: 'Key_N' was not declared in this scope
      scripts/kconfig/qconf.cc:687: error: 'Key_M' was not declared in this scope
      scripts/kconfig/qconf.cc:690: error: 'Key_Y' was not declared in this scope
      
      scripts/kconfig/qconf.cc: In constructor 'ConfigMainWindow::ConfigMainWindow()':
      scripts/kconfig/qconf.cc:1329: error: 'CTRL' was not declared in this scope
      scripts/kconfig/qconf.cc:1329: error: 'Key_Q' was not declared in this scope
      scripts/kconfig/qconf.cc:1331: error: 'Key_L' was not declared in this scope
      scripts/kconfig/qconf.cc:1333: error: 'Key_S' was not declared in this scope
      scripts/kconfig/qconf.cc:1340: error: 'Key_F' was not declared in this scope
      Signed-off-by: NMarkus Heidelberg <markus.heidelberg@web.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      fbb86374
    • M
      kconfig qconf: fix namespace for Horizontal and Vertical enum values · 7298b936
      Markus Heidelberg 提交于
      They were used as QSplitter::Horizontal resp. QSplitter::Vertical, but
      are defined in the 'Qt' namespace.
      
      Fixes the following compiler errors after a quick conversion with 'qt3to4',
      which occured with g++ 3.4.6 and 4.1.2, but not anymore with 4.3.2.
      
      scripts/kconfig/qconf.cc: In constructor 'ConfigSearchWindow::ConfigSearchWindow(ConfigMainWindow*, const char*)':
      scripts/kconfig/qconf.cc:1213: error: 'Vertical' is not a member of 'QSplitter'
      
      scripts/kconfig/qconf.cc: In constructor 'ConfigMainWindow::ConfigMainWindow()':
      scripts/kconfig/qconf.cc:1304: error: 'Horizontal' is not a member of 'QSplitter'
      scripts/kconfig/qconf.cc:1311: error: 'Vertical' is not a member of 'QSplitter'
      Signed-off-by: NMarkus Heidelberg <markus.heidelberg@web.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      7298b936
    • M
      kconfig qconf: fix -Wall compiler warnings · 98403a91
      Markus Heidelberg 提交于
      These compiler warnings occure when adding -Wall to HOSTCXXFLAGS in
      /Makefile
      
      scripts/kconfig/qconf.h: In constructor ‘ConfigInfoView::ConfigInfoView(QWidget*, const char*)’:
      scripts/kconfig/qconf.h:274: warning: ‘ConfigInfoView::menu’ will be initialized after
      scripts/kconfig/qconf.h:273: warning:   ‘symbol* ConfigInfoView::sym’
      scripts/kconfig/qconf.cc:922: warning:   when initialized here
      
      scripts/kconfig/qconf.cc: In member function ‘void ConfigMainWindow::setMenuLink(menu*)’:
      scripts/kconfig/qconf.cc:1498: warning: enumeration value ‘menuMode’ not handled in switch
      scripts/kconfig/qconf.cc:1498: warning: enumeration value ‘listMode’ not handled in switch
      
      scripts/kconfig/qconf.cc: In member function ‘void ConfigMainWindow::saveSettings()’:
      scripts/kconfig/qconf.cc:1664: warning: enumeration value ‘menuMode’ not handled in switch
      scripts/kconfig/qconf.cc:1664: warning: enumeration value ‘listMode’ not handled in switch
      Signed-off-by: NMarkus Heidelberg <markus.heidelberg@web.de>
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      98403a91
  12. 29 1月, 2008 2 次提交
  13. 21 10月, 2007 1 次提交
  14. 26 7月, 2007 1 次提交
    • S
      kconfig: attach help text to menus · 03d29122
      Sam Ravnborg 提交于
      Roman Zippel wrote:
      > A simple example would be
      > help texts, right now they are per symbol, but they should really be per
      > menu, so archs can provide different help texts for something.
      
      This patch does this and at the same time introduce a few API
      funtions used to access the help text.
      
      The relevant api functions are introduced in the various frontends.
      Signed-off-by: NSam Ravnborg <sam@ravnborg.org>
      Cc: Roman Zippel <zippel@linux-m68k.org>
      03d29122
  15. 03 5月, 2007 1 次提交
  16. 15 2月, 2007 5 次提交
  17. 12 1月, 2007 1 次提交
  18. 06 1月, 2007 1 次提交
  19. 14 12月, 2006 2 次提交
  20. 08 12月, 2006 1 次提交
  21. 26 11月, 2006 1 次提交
  22. 09 6月, 2006 4 次提交
  23. 06 5月, 2005 1 次提交
    • A
      [PATCH] Kconfig i18n support · 3b9fa093
      Arnaldo Carvalho de Melo 提交于
      This patch adds i18n support for make *config, allowing users to have the
      config process in their own language.
      
      No printk was harmed in the process, don't worry, so all the bug reports,
      kernel messages, etc, remain in english, just the user tools to configure
      the kernel are internationalized.
      
      Users not interested in translations can just unset the related LANG,
      LC_ALL, etc env variables and have the config process in plain english,
      something like:
      
      LANG= make menuconfig
      
      is enough for having the whole config process in english. Or just don't
      install any translation file.
      
      Translations for brazilian portuguese are being done by a team of
      volunteers at:
      
      http://www.visionflex.inf.br/kernel_ptbr/pmwiki.php/Principal/Traducoes
      
      To start the translation process:
      
        make update-po-config
      
        This will generate the pot template named scripts/kconfig/linux.pot,
        copy it to, say, ~/es.po, to start the translation for spanish.
      
      To test your translation, as root issue this command:
      
        msgfmt -o /usr/share/locale/es/LC_MESSAGES/linux.mo ~/es.po
      
        Replace "es" with your language code.
      
        Then execute, for instance:
      
        make menuconfig
      
      The current patch doesn't use any optimization to reduce the size of the
      generated .mo file, it is possible to use the config option as a key, but
      this doesn't prevent the current patch from being used or the translations
      done under the current scheme to be in any way lost if we chose to do any
      kind of keying.
      
      Thanks to Fabricio Vaccari for starting the pt_BR (brazilian portuguese)
      translation effort, Thiago Maciera for helping me with the gconf.cc (QT
      frontent) i18n coding and to all the volunteers that are already working on
      the first translation, to pt_BR.
      
      I left the question on whether to ship the translations with the stock kernel
      sources to be discussed here, please share your suggestions.
      Signed-off-by: NArnaldo Carvalho de Melo <acme@conectiva.com.br>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: Linus Torvalds <torvalds@osdl.org
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      3b9fa093
  24. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4