Opened 15 years ago

Closed 14 years ago

#136 closed feature request (fixed)

Vim temp system

Reported by: Joe Ciccone Owned by: clfs-commits@…
Priority: trivial Milestone: CLFS Standard 1.2.0
Component: BOOK Version: CLFS Standard GIT
Keywords: vim temp-system Cc:

Description

Add a optional step to build vim in the temp system.

Change History (9)

comment:1 Changed 14 years ago by William Harrington

I do agree with this, and it was brought up a while ago in the IRC channel. In chapter 10 to verify edits done to files, it would be very good to use vim (or some other editor) to view changes rather than grep for the changes or cat and then look through the changes, especially for specs. I suggest vim go into the temp tools so an editor other than a stream editor is available in chapter 10 while building the system. I often find myself opening another terminal to connect then go to the file in the /mnt/clfs hierarchy to check with the host editor.

Any input...?

William

comment:2 Changed 14 years ago by Joe Ciccone

Milestone: CLFS Standard 1.2.0CLFS Standard 1.1.0
Version: CLFS Standard 1.2.0CLFS Standard 1.1.0

I'd love todo this aswell. I havn't tested any methods of building Vim yet. But I'm assuming that it can't be too much different from sysroot.

Apply the cross_compilation patch from the sysroot book.

echo '#define SYS_VIMRC_FILE "/tools/etc/vimrc"' >> src/feature.h
./configure --build=${CLFS_HOST} --host=${CLFS_TARGET} \
    --prefix=/tools --enable-multibyte --enable-gui=no \
    --disable-gtktest --disable-xim --with-features=normal \
    --disable-gpm --without-x --disable-netbeans \
    --with-tlib=ncurses
make
make install
ln -s vim /tools/bin/vi

Then we just need to create a basic vimrc, probably the same one that's suggested in the final system.

I'm pushing up to clfs 1.1.0 from 1.2.0. This is something that should work fairly well thanks to clfs sysroot.

comment:3 Changed 14 years ago by Joe Ciccone

Type: taskfeature request

comment:4 Changed 14 years ago by Joe Ciccone

Milestone: CLFS Standard 1.1.0CLFS Standard 1.2.0
Version: CLFS Standard 1.1.0CLFS Standard 1.2.0

Bumping back up to 1.2.0

comment:5 Changed 14 years ago by Joe Ciccone

Version: CLFS Standard 1.2.0CLFS Standard SVN

comment:6 in reply to:  description ; Changed 14 years ago by William Harrington

Replying to jciccone:

Add a optional step to build vim in the temp system.

Look at this thread for cross compiling vim for the temp system:

http://www.mail-archive.com/vim_dev@googlegroups.com/msg00887.html

I'm working on it as we speak, however, there will be changes need from 64 bit and 32 bit hosts for a variable or two (Particularly int). But that is what needs to be done. vimrc isn't needed. Matter of fact, the temp system doesn't need any vimrc whatsoever, it should just be a default. People can change vimrc if they wish.

comment:7 in reply to:  6 Changed 14 years ago by William Harrington

Replying to kb0iic:

Replying to jciccone:

Add a optional step to build vim in the temp system.

Look at this thread for cross compiling vim for the temp system:

http://www.mail-archive.com/vim_dev@googlegroups.com/msg00887.html

I'm working on it as we speak, however, there will be changes need from 64 bit and 32 bit hosts for a variable or two (Particularly int). But that is what needs to be done. vimrc isn't needed. Matter of fact, the temp system doesn't need any vimrc whatsoever, it should just be a default. People can change vimrc if they wish.

I've used this for the powerpc64 build so far:

ac_cv_sizeof_int=4 vim_cv_getcwd_broken=no vim_cv_memmove_handles_overlap=yes vim_cv_stat_ignores_slash=yes vim_cv_tgetent=zero vim_cv_terminfo=yes vim_cv_toupper_broken=no vim_cv_tty_group=world CC="${CC} ${BUILD64}" ./configure --prefix=/tools --build=${CLFS_HOST} --host=${CLFS_TARGET} --with-tlib=ncurses --with-features=tiny

comment:8 Changed 14 years ago by Joe Ciccone

I already tackled this in clfs sysroot. All we have todo is copy it over.

comment:9 Changed 14 years ago by Jim Gifford

Resolution: fixed
Status: newclosed

Added r4468

Note: See TracTickets for help on using tickets.